Date: 09/15/01
- Next message: ih <email protected>: "[PHP-DEV] Bug #13322 Updated: Still SIGSEGV with DOMXML / double free()"
- Previous message: ih <email protected>: "[PHP-DEV] Bug #13322 Updated: Still SIGSEGV with DOMXML / double free()"
- In reply to: colin: "[PHP-DEV] Re: Bug #12690 Updated: array_unique under windows does not work as it does under linux"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> 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 venaas <email protected>
--Jeroen
-- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: php-dev-unsubscribe <email protected> For additional commands, e-mail: php-dev-help <email protected> To contact the list administrators, e-mail: php-list-admin <email protected>
- Next message: ih <email protected>: "[PHP-DEV] Bug #13322 Updated: Still SIGSEGV with DOMXML / double free()"
- Previous message: ih <email protected>: "[PHP-DEV] Bug #13322 Updated: Still SIGSEGV with DOMXML / double free()"
- In reply to: colin: "[PHP-DEV] Re: Bug #12690 Updated: array_unique under windows does not work as it does under linux"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

