Re: json_encode()
| From: | mike | Date: | Tue, 16 Dec 2008 05:36:59 +0000 |
| Subject: | Re: json_encode() | ||
| References: | 1 2 3 4 5 6 7 8 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-42278@lists.php.net to get a copy of this message | ||
On Mon, Dec 15, 2008 at 8:58 PM, Mark Karpeles <mark@hell.ne.jp> wrote:
> I believe part of the job should be the programmer's job too.
I'm a programmer. I expect json_* functions to encode and decode to
JSON specifications. Not PHP's original interpretation of it...
> Lazy mode is "not that good", as it's going to break things anyway by
> silently doing magic stuff the final developer didn't expect because it
> didn't happen in previous versions.
Okay, well PHP 6's behavior is going to change certain things already.
Hence why I would recommend the change to be in a major version (6.x)
But in the meantime, we're going to be stuck using a construct that
works but does not work to actual specification and we're just going
to "stick with it" because it will be a change?
PHP does "magic" already on a variety of things behind the scenes,
there should be no reason why this is any different.