|
From: | Markus Mützel |
Subject: | [Octave-bug-tracker] [bug #55452] fopen() does not support encoding argument |
Date: | Sun, 10 Mar 2019 11:24:27 -0400 (EDT) |
User-agent: | Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:66.0) Gecko/20100101 Firefox/66.0 |
Follow-up Comment #25, bug #55452 (project octave): Wrt "fgets": I am still not certain we should change its behaviour. At the moment it is (more or less) POSIX conform in behaviour. [1] It might be unexpected if it returned an "unpredictable" number of bytes. Even more so if it also did some kind of automatic conversion. The documentation isn't very precise in what is meant with "character". Sometimes that can refer to a C-char (i.e. a byte or one element of a character array) and sometimes to an "abstract character" (approx. in its Unicode definition). The former meaning is probably implied in the majority of cases. [1]: http://pubs.opengroup.org/onlinepubs/009695399/functions/fgets.html _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?55452> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |