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

Michael S <already5chosen@yahoo.com> writes:

On Sat, 15 Feb 2025 08:37:20 -0800
Tim Rentsch <tr.17687@z991.linuxsc.com> wrote:

[...]

Clearly using fgets() is problematic when the input stream might
contain null characters.  To me it seems obvious that the original
implementors expected that fgets() would not be used in such cases,
perhaps with the less severe restriction that the presence of
embedded nulls could be detected and simply rejected as bad input,
much the same as overly long lines or a final line without a
terminating newline character.

>
My impression is that they didn't spend much time thinking.

I have no idea how much time was spent designing the fgets()
interface, nor do I think it's important to know.  I understand the
limitations of fgets() and don't mind using it in circumstances
where it provides a net positive value.