On Thu, 2008-01-03 at 20:50 +0100, Derick Rethans wrote: > With that statement I don't agree though. It needs to be usefull for a > more general public, and not introduce a huge performance loss for > example.
You're right, I didn't mean that like it sounded. But a feature that maintains backwards compatibility and doesn't have a major disadvantage for those who choose not to use it is almost always good. In this case, it will benefit many, and to those who choose not to use it, they will probably never even notice it's there. So why not? Because it somehow goes against the ideology of some PHP users? I'm sorry but I just don't see that as reason enough to throw away something that could be very useful. PHP is quickly moving from an easy to learn unprofessional scripting language into an enterprise-level scalable language. Look at it's newer enhanced XML capabilities, improved OO engine, and all of the third-party integration libraries. Finer-grained control over an application (which type hinting contributes to) is something that fits the newer and better language that PHP is becoming. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
