|
From: | Kai Torben Ohlhus |
Subject: | [Octave-bug-tracker] [bug #57596] Should the "len" argument of "fgetl" and "fgets" mean bytes or characters |
Date: | Tue, 14 Jan 2020 04:06:26 -0500 (EST) |
User-agent: | Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.117 Safari/537.36 |
Update of bug #57596 (project octave): Status: None => Need Info _______________________________________________________ Follow-up Comment #1: In the manual https://octave.org/doc/v5.1.0/XREFfgetl.html there is > len characters but you are right. I think this was written in the common believe 1 char = 1 byte. As user I would expect "len" characters to be read. What is the point of reading a damaged UTF-8 encoded character at the limit of "len" bytes? But as it is a pure Octave extension, we are free to change/specify that interface, or to deprecate this parameter. grep-ing the Octave sources shows, that it is unused. _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?57596> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |