At 11:31 AM 11/28/2001 -0800, Vlad Krupin wrote: >Hartmut Holzgraefe wrote: > >>Markus Fischer wrote: >> >>> Although my vote doesn't count much here :-) I'm for it... >>> >>> ... but it would be a problem for 4.x I guess because this >>> horribly breaks BC when/if there's a new 4.x release and >>> people start using it. >> >> >>should be no problem to introduce it with 4.2 as we are >>breaking BC in lots of places anyway ... > >I do not have much against this particular proposal, >but I have observed the tendency here (on this mailing list) >to be something like that: "Since we are breaking one thing, >we might just as well let the hell break loose and break >everything else, be it necessary or not." Often times the >"break early, break hard" principle will not work all that well >just because we are not breaking early anymore, and >breaking things just to make a cute feature or two work >might not be such a good idea. > >This is just an observation, don't flame me, but this attitude >is starting to worry me a bit. I can see 4.2 being so different >from 4.0.6 that we might not be able to call it 'php' anymore. > >Just something to watch out for, so we don't go overboard... > >Now, have a good day, everyone
I agree. We should fix problems but people have to remember that no matter what there are lots and lots of users out there and the less we break things, even between major versions, the easier & possible the transition will be for the users. Most PHP users out there aren't php-dev techies who like fixing their old code to work with new versions :) They prefer their old stuff to work. So sometimes we need to break stuff but it should always be done only if it really makes good sense and gives enough benefit. Andi -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
