> So what's the reason you talk about two levels? If you interpret the first three racetracks as generating a sequence of characters, or the last two as generating a sequence of tokens, you get the wrong result.
>> RFC 4627 does that implicitly by saying "The representation of numbers is >> similar to that used in most programming languages.".) > > That's not very precise either, but it's at least telling the reader where to > look further if s/he doesn't understand what's intended. Actually, to the extent that RFC 4627 does define JSON's data model, the result of this simple statement is surprisingly precise. It only stops helping you much when you reach the limits of precision or range (e.g., what to do with 1e400.) > Another problem is that it's not scalable, in the sense that it won't work > anymore if everybody would do it. Right. But then, section 11.8.3.1 of the ES6 draft is an example for why it is tedious to do this. (It is also, I believe, a nice example how easy it would be to get this wrong and that nobody would actually notice a mistake buried in there, unless they do the work to systematically check every detail or to translate it into a machine-checkable form. Fortunately, our number system is relatively stable; I’d hate to maintain a spec that has this level of tedium on something that actually evolves. For added fun, compare with 7.1.3.1.1, which is mostly saying the same thing, but does it in a subtly different way. That’s why ES6 is 531 pages...) > I'm not planning to do any work. I was just trying to point out that the > technical work is not that difficult (after some leaps of faith to take the > 'most obvious' interpretation of racetracks,…). Yep. But if nobody does that work (or, more precisely, admits to having done that work), we simply don’t know whether the statement that triggered this little subthread is true or not. I have made too many stupid mistakes in seemingly simple specs that became obvious only as soon as I used a tool to check the spec. Grüße, Carsten _______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
