|
From: | Andreas Weber |
Subject: | [Octave-bug-tracker] [bug #52681] Bad reading for UTF-8 characters with fscanf() |
Date: | Sun, 17 Dec 2017 14:42:34 -0500 (EST) |
User-agent: | Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.84 Safari/537.36 |
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/
[Prev in Thread] | Current Thread | [Next in Thread] |