Ok... I promised to complete the RFC and here I am. I wrapped the entire idea, PHP implementation of what I'm proposing all in RFC. If you're interested, feel free to review the document, highlight if I missed something and update/add your votes.
http://wiki.php.net/rfc/splclassloader Answering possible questions: 1- Why do not implement a fallback directory? It is implemented as part of include_path lookup. Just add the fallback directory in your include path and you're done. 2- Why not implement addAll, remove, etc? Remove is useless. conditionally add loaders and you're done. AddAll is ok for user land, but we focus on basic stuff, not fluffy implementations. It can be easily done in userland. Cheers, On Tue, Nov 8, 2011 at 1:29 AM, Rasmus Lerdorf <ras...@lerdorf.com> wrote: > On 11/07/2011 07:04 PM, Larry Garfield wrote: > >> If anything, the low degree of communication between "people who write >> PHP" and "people who write in PHP" is, and has long been, one of PHP's >> great weaknesses. I think this entire thread has shown that very well. >> That is something that needs to be addressed, just as much as >> inter-framework communication does. Perhaps moreso. > > This is the second time someone has alluded to that. I don't see a > single core PHP developer weighing in on this thread in the way you > describe. All I see are various framework folks disagreeing with each other. > > -Rasmus > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > -- Guilherme Blanco Mobile: +55 (11) 8118-4422 MSN: guilhermebla...@hotmail.com São Paulo - SP/Brazil -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
