On 12-Jun-2011 17:02 , Junlei Li wrote:
Just a reminder, the maximum value is 2^64 (18446744073709551616) and
2^63 (9223372036854775808) for a unsigned and a signed 8-byte binary
On Mon, Jun 13, 2011 at 1:00 AM, CRPence wrote:
The "bytes in" for the effectively equivalent API [List Network
Connections (QtocLstNetCnn) API] shows as having data type BINARY(8)
which as signed integer would wrap at 2147483647, but as unsigned
integer would wrap at 4294967295.
Ah yes, thanks; although that would be 2^63-1 instead, for signed.
Seems my unsigned was doubly wrong, both for number of bytes and for
having subtracted one.
I had concentrated too much on what appears [on old releases] to be a
10-digit presentation limit on the panel [the part snipped from quoted
reply]. Seems I should not have taken the time to dig up the link to
the API to show off my failing arithmetic skills combined with my
awesome skills at copy\paste ;-) So anyhow, from the F11="Display byte
counts" details on the "Work with TCP/IP connection status" panel, there
appears to be a presentation limit that more closely resembles what
might be reflected by a 4-byte binary\integer variable; i.e. regardless
of what the effectively equivalent API might support.
So for the OP the question remains, if the presentation might reflect
a binary integer wrap versus [what was already described as apparently
not] a decimal wrap.?
This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact