Hi!
this seems like a very good idea to me. this way things default to "just work" (which imho is the PHP spirit), while its brain dead easy to detect misuse.
They not "just work" - they "work" in a wrong way (not usable in any practical application). And E_NOTICE is a non-solution here - if we know that it's wrong enough to put a warning there, why we don't make it right? Why should we put another thing to stumble upon - why people should learn another gimmick "you can write it that way, but you never should do it because it works badly". If they shouldn't write it that way - what would be the reason to allow them to do it instead of giving clear error message that makes it easy to fix? I can understand when such things are left over by BC reasons - but to explicitly design the language in a way that needs footnotes and warnings to code around bad design?
-- Stanislav Malyshev, Zend Software Architect [EMAIL PROTECTED] http://www.zend.com/ (408)253-8829 MSN: [EMAIL PROTECTED] -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
