Re: Namespaces / Autoload - from PHP-DEV - was Re: [PEAR-DEV] [Coding Standards] Loading all files at once
| From: | David Coallier | Date: | Mon, 09 Jul 2007 23:34:36 +0000 |
| Subject: | Re: Namespaces / Autoload - from PHP-DEV - was Re: [PEAR-DEV] [Coding Standards] Loading all files at once | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-47342@lists.php.net to get a copy of this message | ||
On 7/9/07, Alan Knowles <alan@akbkhome.com> wrote:
Just for reference: Namespaces are going in Wednesday to PHP6 CVS! - finally.. Quote about __autoload from internals: "I know, and I use spl_autoload_register. But then I would blatantly suggest to remove __autoload() in PHP6 and force SPL to be compiled into PHP. " "I wouldn't go as far as removing it, but definitely would go as far as not recommending to use it if writing a library or application that includes independent modules (such as libraries). If you application is homogeneous and non-modular, then using it may be ok. " Regards Alan Joshua Eichorn wrote: Alexey Borzov wrote:Do we really wan to talk about this now ? We are still trying to find a settlement on when to remove PHP4 from our dirty hands.. we can say that in about 5 years we can start moving to PHP6 ;-). and btw, iirc, we are using spl_autoload_register if not, then it's defenatly a good thing we should do - but again, we have to wait until there's another discussion on the mailing list about having SPL in the core (the second part of it) in a few months, then in a few more months, we'll have the decision made (without real approval from the community) from some PHP Company about having it or not. My point is: SPL is not even sure to be accepted in the core.I LOVE SPL since it's first day and I have worked a bit on the DirectoryITerator for php6, however, I am really not sure to see it in core (Might have missed something though) -- David Coallier, Founder & Software Architect, Agora Production (http://agoraproduction.com) 51.42.06.70.18Everyone elses argument was the target is people who care about performance but don't run an opcache. I find this equally as odd. But anyway the whole point of autoload is you don't have to set your include path and the only includes that ever happen, come from your autoload code. require_once + autoload is very odd setup -josh -- PEAR Development Mailing List (http://pear.php.net/) To unsubscribe, visit: http://www.php.net/unsub.phpHi, Joshua Eichorn wrote:Trying making this work without setting your include path.Does that mean that the target audience of PEAR2 are people who are unable to properly set the include_path of their PHP installation? Seriously, setting an "include path" (or its equivalent) for libraries is a task that is common amongst almost all programming languages.