Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:43226 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 42675 invoked from network); 2 Mar 2009 16:36:40 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 2 Mar 2009 16:36:40 -0000 Authentication-Results: pb1.pair.com smtp.mail=rquadling@googlemail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=rquadling@googlemail.com; sender-id=pass; domainkeys=bad Received-SPF: pass (pb1.pair.com: domain googlemail.com designates 209.85.220.158 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: rquadling@googlemail.com X-Host-Fingerprint: 209.85.220.158 mail-fx0-f158.google.com Received: from [209.85.220.158] ([209.85.220.158:55795] helo=mail-fx0-f158.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E6/8E-00495-71B0CA94 for ; Mon, 02 Mar 2009 11:36:40 -0500 Received: by fxm2 with SMTP id 2so2081150fxm.23 for ; Mon, 02 Mar 2009 08:36:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:reply-to:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=/fBNeyAEC42TbrBrVrHMGhNorzlHzcnGzLLfPALERUM=; b=nQQ5YK2sU9SRYxBGn76o4enRUky3IZIarjh2dnBOTWYC316nXxkj7T70WmYzlxm0to UyZRQ8pA/sQdV8oZSbGCCo9487cTwL+OxKOustIak4kru6fdG9sj0BkFciK4l8aoTz5v FtwGCJklOGyQBxs+unUOLC0nRenKa4GmiVJqA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; b=NUfQB7oXX5YuNhEGOJlp78hBDlpMpbTyZO7VHYeok7tMSfeGxIMvhXGtQtEEKMP76g nAaIVycmxaZQUpH9NE84/mBE4O9/PJvLyiY/ScLEuVqRuFzlkN2vXZX9fuZotUYLnFBh i4MPrsaS7xb3AmwR8tDDg105aD4kveD8rtGAU= MIME-Version: 1.0 Received: by 10.223.124.75 with SMTP id t11mr6094290far.73.1236011796836; Mon, 02 Mar 2009 08:36:36 -0800 (PST) Reply-To: RQuadling@googlemail.com In-Reply-To: <49AC08EA.5000105@macvicar.net> References: <10845a340903020821v718bc762g243864f7e098ee1c@mail.gmail.com> <49AC08EA.5000105@macvicar.net> Date: Mon, 2 Mar 2009 16:36:36 +0000 Message-ID: <10845a340903020836u67ba1600qd4be7101f4256863@mail.gmail.com> To: Scott MacVicar Cc: PHP Internals List Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Patch and test cases too for From: rquadling@googlemail.com (Richard Quadling) 2009/3/2 Scott MacVicar : > Richard Quadling wrote: >> Hi. >> >> Regarding http://bugs.php.net/bug.php?id=47493, I've supplied a patch >> to the unit tests too. >> >> Any chance this could get committed to 5.2+ >> > > I'm too convinced of the parameter name and I don't think its something > that should be added to 5.2.9 since its a feature. > > Scott > 5.3+ would be OK then. As to the param name, I'm not actually changing the name, just adding another flag. In javascript's terminology,the output is an array ... [] or a hash {} So forcing a hash for arrays is pretty much what would be wanted and I as I comment in the request, we have a "force" option when coming FROM json data ... json_decode ( string $json [, bool $assoc= false [, int $depth= 512 ]] ) And the "name" of the param here is appropriate to PHP's use (assoc is not part of JSON's or JS's terminology). If you can think of a better name for the flag, then I'd be glad to use it. Richard. -- ----- Richard Quadling Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731 "Standing on the shoulders of some very clever giants!"