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

On 09.02.2025 11:50, Michael S wrote:

On Sun, 9 Feb 2025 08:13:10 +0100
Janis Papanagnou <janis_papanagnou+ng@hotmail.com> wrote:
 

[...]

>
I have a _coherent_ file, with a few NL terminated lines of text.

 
I wonder what you mean by "coherent".

A badly chosen word; I noticed it too late only after posting.

I meant consistent with respect to the line terminators (i.e. none
missing, each line [including the last one] has one, no mixture of
LF, CR, LR-LF, etc. (and also no fixed-sized unterminated lines as
we may still know from mainframes, just to be complete).

 

Usually I use fgets() in contexts where I process every line, like
>
    while (fgets (buf, BUFSIZ, fd) != NULL) {
        operate_on (buf);
    }
    // here the status of buf[] is usually not important any more
>
My actual context was different, like
>
    while (fgets (buf, BUFSIZ, fd) != NULL) {
        // buf[] contents are ignored here
    }
    operate_on (buf[]);  // which I assumed contains last line
>

 
It depends on definition of "last line".
What do you consider "last line" of the file in which last character is
not LF?

I consider missing newlines at the end of any text line as a bug.
(And I'm not inclined to use a weaker word than "bug".) YMMV.

The one before the last LF or one after? Your code would get
the latter.

It's a non-issue (for me), as should have got obvious.

Janis