[Octave-bug-tracker] [bug #47741] The scanf family of functions cannot parse 64bit hex numbers on Windows and 32bit Linux

[Mike Miller]

Update of bug #47741 (project octave):

                  Status:                    None => Confirmed              

    _______________________________________________________

Follow-up Comment #1:

Good catch about the length modifier actually being used. I read the help text
but did not test myself, so that is inconsistent.

My preference would be that these functions map exactly to the way they work
in C/C++, which means that the length modifier characters are
platform-dependent rather than operating on sized integers.

If we're going to ignore all length modifiers, then I'm fine with that, and we
always read a intmax_t/uintmax_t.

If we want to actually use the length modifiers, then I would expect them to
work exactly as in the library functions, so "hh" is char, "h" is short int,
"l" is long int, "ll" is long long int. And I would like to add support for
the standard "j", "t", and "z" modifiers as well, and the GNU extensions "L"
and "q" (both are aliases for "ll").

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?47741>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/