[Octave-bug-tracker] [bug #52681] Bad reading for UTF-8 characters with fscanf()

[Andreas Weber]

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

@mmuetzel: It's true that "char" is signed on x86 but it's unsigned on arm for
example.

There are macros "CHAR_MIN" and "CHAR_MAX" which may help.

I had the same problem compiling some OCT files on armhf:
https://stackoverflow.com/questions/46463064/what-causes-a-char-to-be-signed-or-unsigned-when-using-gcc

    _______________________________________________________

Reply to this item at:

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

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