Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:35068 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 20770 invoked by uid 1010); 1 Feb 2008 19:13:42 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 20755 invoked from network); 1 Feb 2008 19:13:42 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 1 Feb 2008 19:13:42 -0000 Authentication-Results: pb1.pair.com header.from=judas.iscariote@gmail.com; sender-id=pass; domainkeys=bad Authentication-Results: pb1.pair.com smtp.mail=judas.iscariote@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 64.233.166.177 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: judas.iscariote@gmail.com X-Host-Fingerprint: 64.233.166.177 py-out-1112.google.com Received: from [64.233.166.177] ([64.233.166.177:23237] helo=py-out-1112.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 5E/BA-31091-56F63A74 for ; Fri, 01 Feb 2008 14:13:41 -0500 Received: by py-out-1112.google.com with SMTP id u77so1285366pyb.16 for ; Fri, 01 Feb 2008 11:13:38 -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:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=6B0VMB2M6a2Ta8e3QgHQpP8WFVocoAKTE8/qYkA0TEI=; b=PsQOgCBlQEjcYsjH90f//6u6vNwfOs4Q+pKSeDT4dadFCXh3R5UFcNgMFGJeLJbjOnlInYnoL2+yDsERdb6op4qF1qGgJhNUFRuCaHEja1xu5CXV4z/WemqNNMD58DJe28HStgzvR31LMVcsrn5CwB8bwvbK0KGu9T52dhHX31g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=a5BVFO/SoKOLSgAcqZUAiPbGQDuhFFPrOoyE/v0Nt8CNXsN+fWPZ1/uoni8QVz2OESNHk3cYStaDgsXh+FlqzZib0Vy6pWl75nXo15ZyAOA56oc3/NS3o4qWwy6A8LaV3gMTkEp6fEJHvTP6cu2lQz5Rwaeb1cEMaSSbGDF4pEw= Received: by 10.65.126.16 with SMTP id d16mr6174372qbn.76.1201893217270; Fri, 01 Feb 2008 11:13:37 -0800 (PST) Received: by 10.64.96.3 with HTTP; Fri, 1 Feb 2008 11:13:37 -0800 (PST) Message-ID: <7d5a202f0802011113x3d141a9fqc577f051b35e6d6b@mail.gmail.com> Date: Fri, 1 Feb 2008 16:13:37 -0300 To: php-dev In-Reply-To: <479A60BA.7030905@zend.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <479A60BA.7030905@zend.com> Subject: Re: [PHP-DEV] json_encode() bug From: judas.iscariote@gmail.com ("Cristian Rodriguez") 2008/1/25, Stanislav Malyshev : > Now this is an easy fix but would lead to bad strings silently converted > to empty strings. The question is - should we have an error there? If > so, which one - E_WARNING, E_NOTICE? I'm for E_WARNING. Yes , E_WARNING is the right thing to have IMHO. -- http://www.cristianrodriguez.net