[jose] .NET JavaScriptSerializer wrt ES6

Anders Rundgren <anders.rundgren.net@gmail.com> Fri, 30 October 2015 14:15 UTC

From: Anders Rundgren <anders.rundgren.net@gmail.com>
To: "jose@ietf.org" <jose@ietf.org>, Michael Jones <michael.jones@microsoft.com>
Message-ID: <56337B62.8010008@gmail.com>
Date: Fri, 30 Oct 2015 15:14:58 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/jose/Zsn4UMEkovrzgdjYC1HLoxPWW60>
Subject: [jose] .NET JavaScriptSerializer wrt ES6
Precedence: list

Hi Mike,
This shows what we actually agree on, non-ES6 systems aren't likely to work with what I'm proposing (well, building) without an upgrade:

C#:
         document["quoting"] = "'hi!'";
         document["floating"] = 0.00005;

After running the JavaScriptSerializer using v4.5 of .NET I got

      {"quoting":"\u0027hi!\u0027","floating":5E-05}

which is technically correct but differs from browsers which always normalize strings and format numbers as specified by ES6:

      {"quoting":"'hi!'","floating":0.00005}

OTOH, a patch, QA, test-suites, and all should be a fairly small task.

http://webpki.org/ietf/es6numberbrowsertest.html
Apparently the edge-case IEEE underflow is a remaining issue in my number converter but I'm not able to tell who's wrong.

Best,
Anders

[jose] .NET JavaScriptSerializer wrt ES6 Anders Rundgren