Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:42278 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 57859 invoked from network); 16 Dec 2008 05:37:02 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Dec 2008 05:37:02 -0000 Authentication-Results: pb1.pair.com header.from=mike503@gmail.com; sender-id=pass; domainkeys=bad Authentication-Results: pb1.pair.com smtp.mail=mike503@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.198.238 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.238 rv-out-0506.google.com Received: from [209.85.198.238] ([209.85.198.238:2273] helo=rv-out-0506.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id B9/14-30437-D7E37494 for ; Tue, 16 Dec 2008 00:37:02 -0500 Received: by rv-out-0506.google.com with SMTP id g37so3092045rvb.23 for ; Mon, 15 Dec 2008 21:36:59 -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=VtnVPWmtl44edSr7gclTMWdrBwzJGyJI8Ilj8iotQMs=; b=RqoaQhQyh4pOmJQK2nDhBfT1pUhg3oKRjI4yDHB4MpYblWUsBCKf1mhPmMNuDfXYb0 fED8VZBMWR48tN+vmYLRwIUaFaRKjuGzlRgResrAdr+p1BWoPbb0D75qyetAmej/QTfF XXZY8j8D6I9+iua4RPL3mpfEY6zrZkGLb1wlU= 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=kvRE+ByBh1Of5TnoGlecz3PMw9oACSs3sXHd8x40+r8e0o3vSY/TUpiXrJ5ig71toN U5/avuPi4xHsmJChMtX9xZH76Dtpb+hyq61GT7MCRmiOLuFfaRFlM57JwdFrhzq+ISd7 QXYi+DaRedBcahJQSop+//V5vi42RX2FhJ7OM= Received: by 10.141.122.1 with SMTP id z1mr4126015rvm.210.1229405819192; Mon, 15 Dec 2008 21:36:59 -0800 (PST) Received: by 10.141.152.1 with HTTP; Mon, 15 Dec 2008 21:36:59 -0800 (PST) Message-ID: Date: Mon, 15 Dec 2008 21:36:59 -0800 To: "Mark Karpeles" Cc: "PHP Developers Mailing List" In-Reply-To: <1229403515.27626.3.camel@localhost> 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> <1229403515.27626.3.camel@localhost> Subject: Re: [PHP-DEV] json_encode() From: mike503@gmail.com (mike) On Mon, Dec 15, 2008 at 8:58 PM, Mark Karpeles 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.