Hello, Rasmus Lerdorf wrote: > > Manuel, please tone down your ranting a bit. You always get yourself > overly worked up over things. A bug was fixed, yes it broke BC, but often
That's because I see people systematically making inconsistent arguments just to contradict me. > fixing bugs will do so. It would be very nice if we could get everything > exactly right the first time around, but that simply doesn't happen. If > everything was frozen it would be years between releases and there would Sure but I made several proposals to prevent the damage that may be caused to users that rely on the behaviour that was broken and none was considered. > be no PHP. This particular fix was done 14 months ago and it hasn't > caused hundreds of people to complain, just you. "Just" me? Thank you for the lack of consideration to my person! :-( Anyway, like myself there is always people that only try to upgrade between major revisions, like from 4.0.0 to 4.1.0 in production sites. Some people just realize that something is broken and immediately downgrade without bothering to complain because it is easier to keep an old version that works rather than upgrading to something that breaks their code for reasons that they probably will not bother to spend time figuring because they have a large code base. The real problem here is not just breaking backwards compatibility, but also doing it without considering other alternatives. I realize that it was a mistake, but at least assume it, provide a work around that does not require developers to discard the broken functions from their code and pay more attention in the future to not make this mistake again, don't you agree? Regards, Manuel Lemos -- 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]
