hi! On Sun, Sep 2, 2012 at 1:04 AM, Stas Malyshev <smalys...@sugarcrm.com> wrote: > Hi! > >>> SPL is not a part of basic language syntax. There are no SPL keywords >>> and no SPL classes used unless you explicitly instantiate those classes. >>> So SPL is different. >> >> End users do not see nor buy the difference between what is Zend/ or >> what is ext/spl (or other) and can't be disabled, like SPL. > > Of course they'd see it. Here it goes again: "There are no SPL keywords > and no SPL classes used unless you explicitly instantiate those > classes". You can not just write some plain PHP syntax and end up having > SPL class. If you use SPL class, you must do "new SplSomeClass" or > something similar. It has nothing to do with disabling.
They are seen and promoted as core features. Whether we like that idea or not is not really relevant. We messed that up by making most of the "Standard" PHP Library an extension for only political and licensing reasons. >> I really think we should consider exceptions, step by step, for the >> language itself, when it makes sense. And the generators RFC is one > > We should consider them, but we should not do it in ad-hoc manner. It > doesn't work ad hoc - this is exactly what keeps giving PHP users grief > and PHP as a project reputation of environment that makes no sense - > introducing stuff in random places without regard to how other parts of > the language work. We can't really change existing code without breaking everything out there. So we somehow have to do it on a case by case basis or for new stuff only. Cheers, -- Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
