Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Lawrence D'Oliveiro <ldo@nz.invalid>
Newsgroups: comp.lang.c
Subject: Re: Buffer contents well-defined after fgets() reaches EOF ?
Date: Wed, 12 Feb 2025 06:16:22 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 17
Message-ID: <vohebl$27cv0$1@dont-email.me>
References: <vo9g74$fu8u$1@dont-email.me> <vo9hlo$g0to$1@dont-email.me>
	<vo9khf$ggd4$1@dont-email.me> <vobf3h$sefh$2@dont-email.me>
	<vobjdt$t5ka$1@dont-email.me> <vobro1$u9fa$1@dont-email.me>
	<vobu9b$12bi8$1@dont-email.me> <voc9d7$13pam$2@dont-email.me>
	<vodi7t$1b6at$1@dont-email.me> <voe7kp$1f0us$3@dont-email.me>
	<voegdf$1hbn6$1@dont-email.me> <voel5v$1kp3m$1@dont-email.me>
	<vog3lp$1sd7k$1@dont-email.me> <voggh9$1v580$1@dont-email.me>
	<vogjse$1vo3l$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Wed, 12 Feb 2025 07:16:23 +0100 (CET)
Injection-Info: dont-email.me; posting-host="bb7caed71241890f8fb0f019c2e611ec";
	logging-data="2339808"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19828ymYHQUi0ewgafT8lwk"
User-Agent: Pan/0.161 (Chasiv Yar; )
Cancel-Lock: sha1:uVgWqEQ05peJQUUlSJI2gXwRTFU=
Bytes: 2018

On Tue, 11 Feb 2025 17:44:30 -0500, James Kuyper wrote:

> On 2/11/25 16:47, Lawrence D'Oliveiro wrote:
>
>> On Tue, 11 Feb 2025 13:07:53 -0500, James Kuyper wrote:
>> 
>>> I just tried it, using gcc  and found that fgets() does set the first
>>> byte of the buffer to a null character. Therefore, it doesn't conform
>>> to the requirements of the standard.
>> 
>> GCC is, however, the closest thing we have to a de-facto standard for
>> C.
> 
> I've no interest in de-facto standards. I'm only interested in de-jure
> standards such as ISO/IEC 9899:2023.

Where is there an implementation that conforms to that?