[Octave-bug-tracker] [bug #50743] textscan produces incorrect results for large (64bit) integers

[Andrew Janke]

Follow-up Comment #4, bug #50743 (project octave):

textscan for large ints appears to be working right in 4.4.0 and the latest
development version.


octave:7> intmax('int64')
ans = 9223372036854775807
octave:8> textscan('9223372036854775807', '%d64')
ans =
{
  [1,1] = 9223372036854775807
}

octave:9> intmax('uint64')
ans = 18446744073709551615
octave:10> textscan('18446744073709551615', '%u64')
ans =
{
  [1,1] = 18446744073709551615
}

octave:11> ver
----------------------------------------------------------------------
GNU Octave Version: 6.0.0 (hg id: 8b0c9dc0799a)
GNU Octave License: GNU General Public License
Operating System: Darwin 17.7.0 Darwin Kernel Version 17.7.0: Fri Nov  2
20:43:16 PDT 2018; root:xnu-4570.71.17~1/RELEASE_X86_64 x86_64


Is this bug still outstanding?

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?50743>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/