Re: File Naming Convention
| From: | Justin Patrin | Date: | Tue, 07 Dec 2004 07:32:12 +0000 |
| Subject: | Re: File Naming Convention | ||
| References: | 1 2 3 4 5 6 | Groups: | php.pear.qa |
| Request: | Send a blank email to pear-qa+get-2118@lists.php.net to get a copy of this message | ||
On Tue, 07 Dec 2004 08:27:16 +0100, bertrand Gugger <bertrand@toggg.com> wrote:
> Hi,
> Lukas Smith wrote:
>
> > Anyways so the aim of this regulation is to define a standard that
> > results in short files names and manageable numbers of files inside
> > any directory and more importantly in being able to easily determine
> > the location of any given class (which is particularily more important
> > since the creation of the __autoload() function in php5).
>
> So far, I don't find much doc about it: __autoload()
> What's the constraint on files naming in it ?
> Is it due to the fact that 1 __autoload() per script
> with eventually many classes to __autoload ?
> What is the directory default there ?
> Is this feature only in the PHP5 objects intro documented ?
> I'm quite afraid if I need to take stuff into account, but nothing
> describe it.
It's that way so that the path of the file tells you what the class
name is or vice-versa.
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?
--
Justin Patrin