> then why does this work in version 4.0.4 ?
It was an implementation side-effect. It was not intentionally.
The same issue as that, for example, you can specify a variable violating
the naming rules by using:
$GLOBALS["0a\n"] = "Some value";
because it would be bad for performance to check for validness of the
variable-name, and it isn't easy to do either. Nevertheless you should not
trust on this capability: It could change in the future.
See also bug 12367, the comments by [EMAIL PROTECTED]
--Jeroen
--
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]
