-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi,
Rasmus Lerdorf wrote: > We should probably have done it this way right from > the beginning, but since we didn't and since we don't really want to > deal with the potential BC issues of changing working code, we have to > add it as an option at this point. As long as the output follows the JSON specs, would there really be any BC issues anyway? The \u syntax is part and has been part of the specs since the beginning. Are these real world concerns? thanks, - - Markus -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHVwcM1nS0RcInK9ARApKRAJ0YIPBZYDzF9dGfo2f01kbaDuxtOACg1CYN TPV8cbTac48uz/xEe1seEtI= =FOW7 -----END PGP SIGNATURE----- -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
