Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:42297 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 960 invoked from network); 17 Dec 2008 10:05:24 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 17 Dec 2008 10:05:24 -0000 Authentication-Results: pb1.pair.com header.from=rquadling@googlemail.com; sender-id=pass; domainkeys=bad Authentication-Results: pb1.pair.com smtp.mail=rquadling@googlemail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain googlemail.com designates 209.85.218.21 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.218.21 mail-bw0-f21.google.com Received: from [209.85.218.21] ([209.85.218.21:41758] helo=mail-bw0-f21.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 11/D0-29584-1EEC8494 for ; Wed, 17 Dec 2008 05:05:23 -0500 Received: by bwz14 with SMTP id 14so5094947bwz.23 for ; Wed, 17 Dec 2008 02:05:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:reply-to :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=tP5Twc/ih90PFqyxbfN/8dMLgzuez4R0WyF/nL0V+us=; b=eabmXlM1GH116qB6DJXr2LrXO6SKIpQJ/NfPmMkMUTYsZy0qtmmNfs3wAVxsmGxPCo 6Nb4tdEHW4QuFiV9gCtucxlmi1ynBvle3SdxYE3PlJQVPIIyVwpKBuQg5mGFLmS0Zp0k lkFTOSQpl0m3Yn9+mKTVyMD8RCXpz4MYLFKEY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=message-id:date:from:reply-to:to:subject:cc:in-reply-to :mime-version:content-type:content-transfer-encoding :content-disposition:references; b=HWsDKznXPUHC7KkRsmKBw457M/MoygeAsnQfNEXql7V1Id2V1WeUNZNGL/N4KoHLDn xy8aGxx5yvZBNVini9Q8z7w8DFznheRx1SQ2k1Hur9UneuTPTHgXtgf0FmQcpdp/o7Ur g76Iv52aTuysC20l9ZDn6MZCTIEb49jgyQHvg= Received: by 10.102.218.5 with SMTP id q5mr186995mug.99.1229508318754; Wed, 17 Dec 2008 02:05:18 -0800 (PST) Received: by 10.103.94.6 with HTTP; Wed, 17 Dec 2008 02:05:18 -0800 (PST) Message-ID: <10845a340812170205k62a33385j14e1730fd71f0b27@mail.gmail.com> Date: Wed, 17 Dec 2008 10:05:18 +0000 Reply-To: RQuadling@GoogleMail.com To: viroteck@viroteck.net Cc: "Scott MacVicar" , "PHP Developers Mailing List" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <494698D3.2030801@lerdorf.com> <10845a340812160348k18bffb0et1e75cf345b5e42cc@mail.gmail.com> <494797BE.3060505@macvicar.net> <10845a340812160606k393ddcedq5fa6a1223392c992@mail.gmail.com> Subject: Re: [PHP-DEV] json_encode() From: rquadling@googlemail.com ("Richard Quadling") 2008/12/16 Robin Burchell : > Settings which change behaviour like that aren't really all that fun > for third party/portable applications developers, e.g. forum software > and the likes. magic_quotes_gpc and others are good examples of this. > > Going back to Rasmus' mail based on his discussion with Douglas, I > think that option #1 (documenting the way it works, and documenting > how to do things "properly") sounds perfectly fine. Ok, I see. Add the optional param to the function and have a one-off hit to the userland codebase to fix the problem. So is this going to be 5.3 or 6.0? Would you expect json_decode() to have the param as well. Considering json_encode() COULD encode non JSON compliant data, should json_decode() also decode non JSON compliant data? Richard. -- ----- Richard Quadling Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731 "Standing on the shoulders of some very clever giants!"