[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: John W. Eaton
Subject: [Octave-bug-tracker] [bug #52681] Bad reading for UTF-8 characters with fscanf()
Date: Wed, 27 Dec 2017 15:29:30 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0

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

This seems like a fairly local change, so I don't see why it can't be

In the corresponding BEGIN_{C,S,CHAR_CLASS}_CONVERSION macros, why not also
cast the integer character that is read to unsigned char instead of just char?
 I see that tmp is a std::string object.  Would a cast like that when
assigning to tmp just not matter?


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]