Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:60983 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 85355 invoked from network); 27 Jun 2012 11:27:30 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 27 Jun 2012 11:27:30 -0000 Authentication-Results: pb1.pair.com smtp.mail=kontakt@beberlei.de; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=kontakt@beberlei.de; sender-id=unknown Received-SPF: error (pb1.pair.com: domain beberlei.de from 209.85.217.170 cause and error) X-PHP-List-Original-Sender: kontakt@beberlei.de X-Host-Fingerprint: 209.85.217.170 mail-lb0-f170.google.com Received: from [209.85.217.170] ([209.85.217.170:50084] helo=mail-lb0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id B5/23-02132-02EEAEF4 for ; Wed, 27 Jun 2012 07:27:30 -0400 Received: by lbgc1 with SMTP id c1so1687752lbg.29 for ; Wed, 27 Jun 2012 04:27:26 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=aH0jdBwU7bilD7SjA9UVeSNo0RimRd/Ll+W2QXHXe8Y=; b=AP14we4FkQpYS7kr+Y+tyg/1eLzLoUd5TwlpqAYNSmDD12HXOheLIQxZ8JQO1/0FGG nCSyS2f81wHeUopSgdBVTqxqh8RBHrJYqc5LmTu5i+AbctltGYsKJYUfrpLbYJrDtyTC tYvoYJ6PNy0xagPUbUekGoOv8kzWNhbCoCH90kn4WK7uTaO35KOeFATxt6GAtQr6yEgL PIcBKu4EWHxUgihdnJDovcKyTU2keUpoOuobCxGfUsOImmLKJ0k8xQcRPJha8tSBsQ22 GtofM8+Z13qCv/ya7mrko4ueG1X1j1xmSWjLGXna8sX+Z+ErHIf7+86HTcUEeIknxtPm AyRA== MIME-Version: 1.0 Received: by 10.152.146.169 with SMTP id td9mr19946888lab.42.1340796445863; Wed, 27 Jun 2012 04:27:25 -0700 (PDT) Received: by 10.112.98.131 with HTTP; Wed, 27 Jun 2012 04:27:25 -0700 (PDT) X-Originating-IP: [178.200.247.30] In-Reply-To: <4FEA489D.1010601@sugarcrm.com> References: <20120621141241.GA25789@analysisandsolutions.com> <4FE33EDF.2000409@lerdorf.com> <4FE61E9D.5050908@sugarcrm.com> <4FE734C4.2010706@lerdorf.com> <4FEA489D.1010601@sugarcrm.com> Date: Wed, 27 Jun 2012 13:27:25 +0200 Message-ID: To: Stas Malyshev Cc: Nikita Popov , Rasmus Lerdorf , Gustavo Lopes , "internals@lists.php.net" Content-Type: multipart/alternative; boundary=e89a8f234589df304e04c3727f64 X-Gm-Message-State: ALoCoQn8vROVkgOBGpjfNKeRL4Z8Dh8AnOe+otRhuXKG/FErGwRa3lb4BUEGaXQbzw3ogvZHWMOC Subject: Re: [PHP-DEV] json_encode() behavior for incorrectly encoded strings From: kontakt@beberlei.de (Benjamin Eberlei) --e89a8f234589df304e04c3727f64 Content-Type: text/plain; charset=ISO-8859-1 On Wed, Jun 27, 2012 at 1:41 AM, Stas Malyshev wrote: > Hi! > > > Makes sense to me. So should I do this? Remove warnings + add string > > parameter for json_last_error? > I think its weird that the parameter is called $error_string and setting it to true means returning an array. Why not in the spirit of others have a new function json_last_error_msg() or something similar? > > Looks fine. > -- > Stanislav Malyshev, Software Architect > SugarCRM: http://www.sugarcrm.com/ > (408)454-6900 ext. 227 > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > --e89a8f234589df304e04c3727f64--