Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:42273 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 1569 invoked from network); 15 Dec 2008 21:18:38 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 Dec 2008 21:18:38 -0000 Authentication-Results: pb1.pair.com smtp.mail=mike503@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=mike503@gmail.com; sender-id=pass; domainkeys=bad Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.198.225 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: mike503@gmail.com X-Host-Fingerprint: 209.85.198.225 rv-out-0506.google.com Received: from [209.85.198.225] ([209.85.198.225:16722] helo=rv-out-0506.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 73/C1-24547-DA9C6494 for ; Mon, 15 Dec 2008 16:18:38 -0500 Received: by rv-out-0506.google.com with SMTP id g37so2911702rvb.23 for ; Mon, 15 Dec 2008 13:18:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=SyctoFnPK0f0CQYeAMPmi5Fj85ycdjTBbXgxcERYz8c=; b=InNEfGOSCJW35VsaC5ynXdsASgqX8f+J4XratHgxWSvAHqu8ZanBvEksiTAFqp2kc8 g97lpGoptjOv/aFYpFc8pcFEMlWOTzCdSgKF5j2mvvdGPwsbBjgSTY+dyiTQAuLLoMKW AcRXw7MljzpQf2IOGZOb5ZoQd4iM6eDQCHC2A= 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=WrWfYPMKLZz1Qg4mip3ZvSFltNMNoiJyjecvaumqP8g/rwwjpcZiw3mKhv7tVTyB2F OsHnJ6ECCIOoLEFjlBX7F65wrczHaEs5sZy+Fro5AQwknkwyGcWD+zrVB78I1tI0vlfL fqNbJIqkZIUKwAV4CYAGxnswtENMdl7ZD2Fh4= Received: by 10.141.193.1 with SMTP id v1mr3918589rvp.186.1229375914716; Mon, 15 Dec 2008 13:18:34 -0800 (PST) Received: by 10.141.152.1 with HTTP; Mon, 15 Dec 2008 13:18:34 -0800 (PST) Message-ID: Date: Mon, 15 Dec 2008 13:18:34 -0800 To: "troels knak-nielsen" Cc: "PHP Developers Mailing List" In-Reply-To: <98b8086f0812151310v29603f68kafdb168c6c4e94e9@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <494698D3.2030801@lerdorf.com> <7977336F527D4A70B0E4DD2870708686@VEGA> <98b8086f0812151310v29603f68kafdb168c6c4e94e9@mail.gmail.com> Subject: Re: [PHP-DEV] json_encode() From: mike503@gmail.com (mike) On Mon, Dec 15, 2008 at 1:10 PM, troels knak-nielsen wrote: > I, for one, think that the only sane choices are 1 or 2. The third > option is way too magic, and will end up confusing people. In that case I would have to go for #2. Personally I want to see PHP be as standards-compliant and compatible with everything out there. I don't want non-standard behaviors in PHP to be the things that make it a harder sell when I am pushing it in everything I do. This is a language interoperability issue (more or less) and rather than being lazy and persisting the same behavior, I am trying to push very hard to make it work as JSON consumers expect.