On 21 April 2010 11:46, Adi Nita <adi.n...@gmail.com> wrote: > I cannot agree with the idea of preferring > working applications to good working applications.
Except that's not what's at stake. The application does not become one bit better or worse by using an updated function that's more consistent with other functions. The *language* is what might become better or worse by the change, not any applications. The *side-effect* however, is that you're forcing incredible amounts of developers to fix code if they want to move it to a newer version of PHP. With the risk of having tons of code break or just never migrated to newer versions of PHP with all the problems which that creates. A better option would probably be to introduce functions that essentially do exactly the same as the old ones but consistently with the other functions. Then deprecate the old functions slowly - no instant BC break and people can migrate to the new proper functions in good time. Regards Peter -- <hype> WWW: http://plphp.dk / http://plind.dk LinkedIn: http://www.linkedin.com/in/plind Flickr: http://www.flickr.com/photos/fake51 BeWelcome: Fake51 Couchsurfing: Fake51 </hype> -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
