Thanks for the clarification, Anders.
If you are working from Nashorn, the simplest way to enforce JS formatting is
to coerce the Java number (whatever type it is) to a JS number, e.g. using
unary + operator.
If you need this in Java core libs, the place to discuss this would be the
On 2018-01-29 15:49, Sundararajan Athijegannathan wrote:
Just to be clear. so.. do you want a toString (static method?) variant
in java.lang.Double class as per this specification?
I don't think this is a major issue because all fundamental JSON types anyway
needs be dealt with separately or
Just to be clear. so.. do you want a toString (static method?) variant
in java.lang.Double class as per this specification?
-Sundar
On 29/01/18, 7:45 PM, Anders Rundgren wrote:
On 2018-01-29 14:52, Hannes Wallnöfer wrote:
Hi Anders,
I think I lack the context required to understand what
On 2018-01-29 14:52, Hannes Wallnöfer wrote:
Hi Anders,
I think I lack the context required to understand what you’re asking for. Can
you explain how transmitting numbers/doubles in JSON should work and how the
static method you’re asking for would enable this?
Sure. Signatures depend on
Hi Anders,
I think I lack the context required to understand what you’re asking for. Can
you explain how transmitting numbers/doubles in JSON should work and how the
static method you’re asking for would enable this?
Also, is there a document somewhere describing the IETF standardization work
