copy off the internet from
people who know better.
In short, I don't want to see "error_reporting(E_NONE | E_ERROR);" in
anybody's PHP code. Even if it is harmless.
Maybe I'm just a little too wound up about such things, though. Just my
two cents.
--
Tyler
27;s not meant to combine
with the other predefined constants. 0 is special. 0 doesn't play
nicely with others.
This is obviously an edge case, and a less experienced developer would
hopefully learn very quickly the right way to do it, but I don't like
the idea of giving people ammo to shoot a
Why not use both names?
For all of those distributing frameworks and such, use "package". And
for everybody else, who just wants to shorten their class names, use
"namespace".
It's probably easier said than done, but why not just alias one to the
other?
Tyler
--
PHP Internals - PHP Runtim
That was just a crappy test case I put together really quickly, but I do see
you are correct. I was so focused on ampersands being the issue that the
simple and correct solution eluded me.
Sorry to bother you.
Tyler Lawson
-Original Message-
From: Rasmus Lerdorf [mailto:[EMAIL
reat"]=>
string(0) ""
}
With this patch it would be:
array(4) {
["data"]=>
string(42) "This is my data \u0026 it is really great"
}
Tyler
-Original Message-
From: Antony Dovgal [mailto:[EMAIL PROTECTED]
Sent: Friday, April 27, 2007 3:59 PM
To: T
Hello,
I hope this is the right place for this, as I'd like to post a patch for
your consideration to the way the JSON handles ampersands. I have had
problems sending JSON data back and forth over POST requests, where an
ampersand separates variables. This patch will convert "&" into "\u0026",
w
