On Nov 4, 2017, at 2:00 PM, Jim Crate wrote:
> Have you tried your favorite scripting language? Most (ruby/python/perl) have
> good JSON support.
>
> Alternatively, you could try a standalone binary parser, possibly in
> combination with curl. I haven’t used this one but it looks interesting.
On Nov 1, 2017, at 3:47 PM, Justin Leavens via 4D_Tech <4d_tech@lists.4d.com>
wrote:
> Is it possible to work with a 64 bit integer that's being returned to me in
> an object from an HTTP call? I can't seem to avoid it being turned into
> "-1.502644539978e+18". I also have a POST that requires me
Hi Justin,
in this case, use low-level routines for the communication (receive BLOB for
example or some equivalent using Keisukes cUrl Plugin) and parse the received
data „by hand“.
Tedious, but you have full control.
> Am 03.11.2017 um 00:12 schrieb Justin Leavens via 4D_Tech
> <4d_tech@lists
Keisuke Miyako wrote
> it seems correct that a number is mapped to real, according to JSON
> specification
> ...
>
> if you must exchange Int64, I think it is the responsibility of the sender
> to use string.
>
>> 2017/11/03 3:56、Justin Leavens via 4D_Tech <
> 4d_tech@.4d
>> のメール：
>> Unfortunat
it seems correct that a number is mapped to real, according to JSON
specification
> number
> int
> int frac
> int exp
> int frac exp
> int
> digit
> digit1-9 digits
> - digit
> - digit1-9 digits
> frac
> . digits
> exp
> e digits
> digits
> digit
> digit digits
> e
> e
> e+
> e-
> E
> E+
> E-
ht
4D Tech mailing list wrote
> Yeah, if 4D isn't working, try NTK. In either case, if you can get at the
> value as raw text then you'll be able to find text --> 64-bit conversion
> code. The question in 4D at that point is how to store it. I know it's a
> field type, but can you touch it with anythi
> Le 1 nov. 2017 à 21:16, David Adams via 4D_Tech <4d_tech@lists.4d.com> a
> écrit :
>
> I know it's a field type, but can you touch it with anything other than SQL?
I'm wondering since a while about this: 64 bit is 128/2, 128 is a uuid, a uuid
can be managed in langage as hexadecimal string a
Yeah, if 4D isn't working, try NTK. In either case, if you can get at the
value as raw text then you'll be able to find text --> 64-bit conversion
code. The question in 4D at that point is how to store it. I know it's a
field type, but can you touch it with anything other than SQL?
Is it possible to work with a 64 bit integer that's being returned to me in
an object from an HTTP call? I can't seem to avoid it being turned into
"-1.502644539978e+18". I also have a POST that requires me to pass back the
64-bit int value. I would use 4D or NTK for the object handling if it made
9 matches
Mail list logo
