--- In [email protected], "entropyreduction" <[EMAIL PROTECTED]> wrote: > > --- In [email protected], "Sheri" <sherip99@> wrote: > > > > --- In [email protected], "entropyreduction" > > <alancampbelllists+yahoo@> wrote: > > > > > > > > local hexstr="3fd40c00" > > > > local b=binary.from_hex(hexstr, 8) > > > > binary.default_get_set_type("n") > > > > binary.set_base(0) > > > > win.debug(binary.version, "value:", binary.get_bytes(b, 0, 3, "n")) > > > > > > > > and debug says: 0054h value: 3fd40c00 > > > > Ok, but the result appears to be incorrect: > > > > 0054h value: 1070861312 instead of > > 0054h value: 840767 > > win.debug(hexstr, win.hex(binary.get_bytes(b, 0, 3, "n"))) > > returns two identical fout byte hex values. Not for you? >
Yes it does. That was fixed. Then support for 8 byte numeric got added. I'm fairly ignorant about using binary. In a previous message I asked and you seemed to confirm that "numeric" was going to convert the binary block derived from "3fd40c00" to 840767. How to do it otherwise was described here: http://tech.groups.yahoo.com/group/power-pro/message/33372 Probably a misunderstanding on the issue. I find the figure that is getting computed (1070861312) described elsewhere as "decimal".
