Re: Buffer contents well-defined after fgets() reaches EOF ?

On 14.02.2025 18:22, Kaz Kylheku wrote:

[ ... ]
 
It would be good if fgets nuked the terminating newline.
 
Many uses of fgets, after every operation, look for the newline
and nuke it, before doing anything else.
 
There is a nice idiom for that, by the way, which avoids an
temporary variable and if test:
 
   line[strcspn(line, "\n")] = 0; 

 
This is nice.
 
In the test code which was the base of this thread I'm relying
on the existing '\n' and use   buf[strlen(buf)-1] = '\0';   to
remove the last character.
 

[...]
 
We have decided in the C world that text does not contain zeros.
 
This has become so pervasive that the remaining naysayers can safely
regarded as part of a lunatic fringe.
 
Software that tries to support the presence of raw nulls in text is
actively harmful for security. 

 
Actually, in the same code, I'm also using the strtok() function
to iterate over the buffer to get pointers to the separate tokens;
if I'm not mistaken, that function places '\0' characters in the
buffer to separate the string tokens. This is very efficient and
(since the original buffer data isn't necessary any more) there's
no problems (here) with its data interspersed with '\0'; strings
(the tokens) get accessed through the returned pointers, and the
buffer is just the physical (now sort of "binary") storage.
 
Janis
 

[...]