Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:42291
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.221.20 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references;
        b=xdwoDFgyH8s9+CghtyM8ZjaT4iVWOHtyw4VyXPIQKLau+ucP6GC/8wwMwXsMErPqyZ
         IJCXpnwXwHekQXTXieYAB8b8pE5y02HLzAUn05MuC4PjggNm/Gj5CZQytAbgLNrnz1kk
         s8UDedcZI5ptCb8dUnmRhtiD5BtEDsTKcxR+Y=
Message-ID: <98b8086f0812160655q4970b6c9ga7898ec5af1a31e9@mail.gmail.com>
Date: Tue, 16 Dec 2008 15:55:55 +0100
To: RQuadling@googlemail.com
Cc: "PHP Developers Mailing List" <internals@lists.php.net>
In-Reply-To: <10845a340812160606k393ddcedq5fa6a1223392c992@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <494698D3.2030801@lerdorf.com>
	 <bd9320b30812151009t29bc6283m79f8985022cd7e2b@mail.gmail.com>
	 <10845a340812160348k18bffb0et1e75cf345b5e42cc@mail.gmail.com>
	 <494797BE.3060505@macvicar.net>
	 <10845a340812160606k393ddcedq5fa6a1223392c992@mail.gmail.com>
Subject: Re: [PHP-DEV] json_encode()
From: troelskn@gmail.com ("troels knak-nielsen")

On Tue, Dec 16, 2008 at 3:06 PM, Richard Quadling
<rquadling@googlemail.com> wrote:
> Would it be at all possible to have an ini setting json.strict_encode = On
>
> So, my code doesn't change, but I can activate it globally.
> Essentially I don't want to shoot myself. I don't want to take the
> safety off.

I think we have lots of prior examples of why it's a bad idea to
change language semantics with a global setting.

--
troels