Well no, I guess you don't want to, but then do you want to keep adding new features following no specific naming method? Users I know of already complain about the lack of standard naming throughout PHP.
As there are already alot of changes in PHP6, would it really hurt more to change to one standard naming system? Would it be better for the future? You're worried about conforming to a single naming standard, and that it might put old users off. At the same time, your looking at introducing many other features, like namespaces, which many people hate. No body I know of (assuming that they are sane) would complain if a standard naming system was adopted. Most of them would feel that the quality of the language has just been given a large boost. I won't sit here and take the "running away from the language", knowing that bigger more confusing and perhaps less useful changes will be implemented. To everyone taking part in PHP6 development, thanks for the work, just don't let the users down. And to everyone who has worked on PHP, thank you for giving me a simple OOP capable language! On 11/22/05, Robert Deaton <[EMAIL PROTECTED]> wrote: > On 11/22/05, Rowan Lewis <[EMAIL PROTECTED]> wrote: > > Well, this is all OK. I guess, even if it means PHP will remain messy > > for more years yet. > > > > But can someone point me as to why this (backwards) choice has been made? > > > The current function naming scheme being messy is really a subject of > personal opinion. I personally think that if it comes to a point where > all the functions are replaced with ones like you outlined above, I'd > be running away from the language. > > Not to mention backwards compatability, do we really want to piss off > every person that has coded in PHP over the last few years? > > -- > --Robert Deaton > -- ____ Rowan Lewis (AKA. The Wolf) -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
