All, There has been a lot of discussion unto the merit of this feature. That's fine.
What I'd really like to know before proposing this is what can be improved in this RFC. For example: someone (Stas) brought up that it was weird that all three types (Class, Function, Constant) are served by a single register function (and multiple can be served by a single autoloader). Personally, I see this as a significant simplification advantage, but I can see if others don't. If you don't, can we please try to ideate around coming up with a better syntax? Another example: I've received a lot of feedback that using the "php" root namespace is weird and unexpected. Does anyone agree? Should that be changed prior to proposing this feature? Let's try to improve this RFC to be the best it can prior to proposing and voting. Even if you don't think it's necessary, there are surely things you think can be improved (and hence everyone wins). Thanks Anthony On Sat, Aug 31, 2013 at 7:04 PM, Florin Patan <florinpa...@gmail.com> wrote: > On Sun, Sep 1, 2013 at 12:36 AM, Vartolomei Nicolae > <nvartolo...@gmail.com> wrote: > >> personally Ithink it would be nice if we could provide a way for > const/function autoloading. > > So you will create files for constants? One file with a single line > defining a constant? > > > > Did I understood something wrong? > > > > kindly, > > nvartolomei > > > > Hi, > > > Yes, you understood it wrong. You can have one function / const in a > file if you want, but you can also have a bunch of them in a file > like you have today with classes. And from what I read in the RFC, > someone else who read it could confirm if I'm right or wrong, there's > no mandatory function / file to use this so you can use it like the > current autoloader for classes is working. > > This will be optional to use, like the current autoloader, which is > why we don't have PSR-0 in Core (maybe we should have a thread about > this sooner or later) and I've had plenty of use cases for a feature > like this. Who knows, maybe we'll have PSR-Y Autoload Reloaded which > will cover this as well :) > > Like it has been pointed out already, it also allows the language to > be complete in what's offering and help some users along the way. > > Do you, or anyone else, have a real reason to be against this rather that: > - I don't like it > - I don't/won't use it > - why do we need it? > - it doesn't belong to the language > - etc. > > So, my opinion as a PHP user is that it's a nice addition to the > language and even if I won't use it, as long as it won't affect the > global performance, I can live with it. > > > > Regards, > Florin > ---- > Florin Patan > https://github.com/dlsniper > http://www.linkedin.com/in/florinpatan >
