Hello Jani, even apart from reflection your proposal seems yery good to me. And we would have a good way to suggest what to keep inside php and can really be relied on. Sounds good :-)
regards marcus Saturday, November 19, 2005, 12:16:43 PM, you wrote: > On Sat, 19 Nov 2005, Zeev Suraski wrote: >> >> At 03:49 19/11/2005, Andi Gutmans wrote: >>> As I mentioned to Marcus, it seems odd to me to move reflection in the >>> first >>> place. It seems to me to be very much a language feature and in my opinion, >>> should always be enabled. I can't really see a good reason for this move. >> >> I have to say that I don't see any good reason for this either. The idea of >> "let's make it less broken" is vague, I don't see any reason why >> extensionizing it would help any. >> >> The only advantage I heard so far is that various users are likely to bump >> into various problems, which may make Jani very happy, but is that a real >> reason to go on? :) > I'm not the only one in the world who does not use that and does not need > it and would like to be able to disable it on will.. > I'm not proposing (and never did) to make it disabled by default. > Perhaps we need to extend the --disable-all configure option: > --disable-all=everything|most > Where 'most' is the default and everything for us "purists" like you > like to > say. What I am aiming with all the modularization is to be able to have > a very lean PHP build with ONLY the things I allow to be used in our > projects.. > And also getting as many of these "insignificant" memory/speed eaters > out. > Streams create oceans, you know? :) > --Jani Best regards, Marcus -- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
