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

On 09.02.2025 16:27, Andrey Tarasevich wrote:

On Sat 2/8/2025 11:13 PM, Janis Papanagnou wrote:

But now I wanted to ignore all data that I got for fgets() != NULL
in the loop. And I hoped that *after* the loop the last read data is
still valid.

 
As Michael already noted it depends on what you consider as the last
piece of valid data in your file.

I have a strong opinion of a text file concerning line terminators;
I answered that in my reply Michael.

Say, what do you want to see as "the
last line" in a file that ends with
 
  abracadabra\n<EOF here>
 
?
 
Is "abracadabra" the last line? Or is the last line supposed to be empty
in this case?

If "\n" is a string literal (2 characters, '\' and 'n') then it's an
incomplete line (as to my standards), if it's meant as a <LF> control
character then it's complete. (Similar with <CR> on old Apple/Macs and
<CR><LF> on DOS-alike systems.)

Janis