Re: File Naming Convention

On Tue, 07 Dec 2004 08:55:04 +0100, bertrand Gugger <bertrand@toggg.com> wrote: > Justin Patrin wrote: > > >Net/Monitor/Service/HTTP.php holds the class Net_Monitor_Service_HTTP. > >Similarly if you want to load the class Net_Monitor_Service_HTTP you > >can require_once Net/Monitor/Service/HTTP.php'. > > > >I don't understand why you're asking. What kind of different naming > >scheme would you use? > > > > > > > From now up no other system as this one. > If I make a class A_B_C then it needs to be in A/B/C.php > if I like future user to may use __autoload() with it. > All that is a OO nonsense. > Should we say OFO: Object File Oriented ? > or perhaps FOO ? ....Our classes are named based on their class heirarchy. Since PHP classes can only inherit from one class, this makes perfect sense. As I said, we do this as an easy way to find the source code for the class you're looking for. It's a PEAR standard. Again I ask, what other scheme would you propose? > Thanks, Justin, I can now understand why PHP scripters fear this > __autoload() so much. I don't get this at all....why would someone fear __autoload()? It can be very useful. -- Justin Patrin