Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:85621 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 26316 invoked from network); 1 Apr 2015 02:31:30 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 1 Apr 2015 02:31:30 -0000 Authentication-Results: pb1.pair.com header.from=yohgaki@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=yohgaki@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.169 as permitted sender) X-PHP-List-Original-Sender: yohgaki@gmail.com X-Host-Fingerprint: 209.85.214.169 mail-ob0-f169.google.com Received: from [209.85.214.169] ([209.85.214.169:33603] helo=mail-ob0-f169.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C8/C6-19757-0885B155 for ; Tue, 31 Mar 2015 21:31:28 -0500 Received: by obvd1 with SMTP id d1so58124557obv.0 for ; Tue, 31 Mar 2015 19:31:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=Cg3eKapGYcKHPmwEUEmsPh6eHnkdaakdUWAGfJ2BtIk=; b=e+101rZBQmwIvd20B8HUFXca9eitVepLyp8Uie5DHhQOpD/FPYOgXIE8rTlh3VIXWr U/WHfUqsptn7dQZvBI5bqMzwF2wsqdv18GjYuEfS0ga6HlAxeZcWKIfW5JVlPnCEM7O1 NS7H5trgWq5NH6B0gW8kZbdOhIDKpvqRrAWrReqAm9LJb9oQb+zPwlu1TtbO4c41s7ZM u/s03SwpNnNctq1qCq7kxbcOYB4qF7dArk9lMSW0ovHtTNTl7Zs3WJM9OPEGVlKd678N O4K3ZvdfSTbCylzgD4AkGx3Zxfk0wf21nJj8GxLZbZRecTHVApk99jdnk058ofhHJtTS P6Ag== X-Received: by 10.182.39.195 with SMTP id r3mr37245274obk.44.1427855484388; Tue, 31 Mar 2015 19:31:24 -0700 (PDT) MIME-Version: 1.0 Sender: yohgaki@gmail.com Received: by 10.202.104.196 with HTTP; Tue, 31 Mar 2015 19:30:44 -0700 (PDT) In-Reply-To: References: Date: Wed, 1 Apr 2015 11:30:44 +0900 X-Google-Sender-Auth: 3xkbHrBRL9HSmbHkPFckPvOQodA Message-ID: To: Jakub Zelenka Cc: PHP internals list Content-Type: multipart/alternative; boundary=001a11c35eb0f00c700512a082ce Subject: Re: [PHP-DEV] JSON float number as string From: yohgaki@ohgaki.net (Yasuo Ohgaki) --001a11c35eb0f00c700512a082ce Content-Type: text/plain; charset=UTF-8 Hi Jakub, On Mon, Mar 30, 2015 at 5:45 PM, Jakub Zelenka wrote: > On Mon, Mar 30, 2015 at 1:07 AM, Yasuo Ohgaki wrote: >> >> "int" should be fixed also. >> http://3v4l.org/95dHM >> >> > We have already fix for this: JSON_BIGINT_AS_STRING ( > http://3v4l.org/vYXUk ) > Excellent. > > >> So option may be JSON_SCALAR_AS_STRING or >> additional JSON_INT_AS_STRING. >> >> > I was actually thinking about JSON_INT_AS_STRING anyway as it might be > useful for type consistency in decoding (when decoding number that are > close to bigint limit) and allowing safe encoding from 64bit to 32bit. > However this is a bit more controversial so I plan to open a new thread > about it. > There are too many options (4 options to be exact) for JSON to work safely under HTML context currently. If user would not like to loose int/float information, 6 options are needed. Number of options are better to be reduced, so big +1 for string raw data by default. It may be better to have JSON_HEX_HTML_CHARS = JSON_HEX_TAG | JSON_HEX_AMP | JSON_HEX_APOS | JSON_HEX_QUOT also. Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net --001a11c35eb0f00c700512a082ce--