Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:42298 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 11560 invoked from network); 17 Dec 2008 10:51:25 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 17 Dec 2008 10:51:25 -0000 Authentication-Results: pb1.pair.com header.from=indeyets@gmail.com; sender-id=pass; domainkeys=bad Authentication-Results: pb1.pair.com smtp.mail=indeyets@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.44.30 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: indeyets@gmail.com X-Host-Fingerprint: 74.125.44.30 yx-out-2324.google.com Received: from [74.125.44.30] ([74.125.44.30:45106] helo=yx-out-2324.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 9B/E2-29584-BA9D8494 for ; Wed, 17 Dec 2008 05:51:24 -0500 Received: by yx-out-2324.google.com with SMTP id 3so1555531yxj.83 for ; Wed, 17 Dec 2008 02:51:21 -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=tlF01GivR+tX+vf7nxuYovoTvLdJ9IIrwzpAkrcDwDo=; b=G8nkXRAv1TZKLeX8qLYGCHS+R5so8hVABOljs/nHlYC+ZOf1h7CDKQk0ynglVs/nF1 1sMgSpb79CVIk9KSgu2blScYvBo6JXn9m8C4zHjv3JXLWLakxBN5qs9Z9xSeH2QLUxey 65k02VAxkKn21/0NGhE30Jf6Gs237s+RopDgE= 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=NJRxfzyvQoXRVsWgQG8w64W4jeuTYoweRCywhHwK1xDscUc1FbfZ5PiUIRNeWeLFNw xelIAoswiYoMPdJ2HTVNNfb9P211JcjZKzjpmbJfsrayC+5+mbblXO1W1eBaTdGbwc+M bj1KOXG2AhOUx8nYR4fXUponJwVmEmu5zzLMY= Received: by 10.100.152.2 with SMTP id z2mr343255and.37.1229511081101; Wed, 17 Dec 2008 02:51:21 -0800 (PST) Received: by 10.100.93.10 with HTTP; Wed, 17 Dec 2008 02:51:21 -0800 (PST) Message-ID: Date: Wed, 17 Dec 2008 13:51:21 +0300 To: RQuadling@googlemail.com Cc: viroteck@viroteck.net, "Scott MacVicar" , "PHP Developers Mailing List" In-Reply-To: <10845a340812170205k62a33385j14e1730fd71f0b27@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> <10845a340812160348k18bffb0et1e75cf345b5e42cc@mail.gmail.com> <494797BE.3060505@macvicar.net> <10845a340812160606k393ddcedq5fa6a1223392c992@mail.gmail.com> <10845a340812170205k62a33385j14e1730fd71f0b27@mail.gmail.com> Subject: Re: [PHP-DEV] json_encode() From: indeyets@gmail.com ("Alexey Zakhlestin") On Wed, Dec 17, 2008 at 1:05 PM, Richard Quadling wrote: > Considering json_encode() COULD encode non JSON compliant data, should > json_decode() also decode non JSON compliant data? it should decode as much as it can without any warnings (as long, as there's no ambiguity) -- Alexey Zakhlestin http://www.milkfarmsoft.com/