Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Keith Thompson <Keith.S.Thompson+u@gmail.com>
Newsgroups: comp.lang.c
Subject: Re: C90 fpeek
Date: Thu, 23 Jan 2025 21:13:29 -0800
Organization: None to speak of
Lines: 18
Message-ID: <87plkc6bgm.fsf@nosuchdomain.example.com>
References: <vmv082$1u6pm$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain
Injection-Date: Fri, 24 Jan 2025 06:13:30 +0100 (CET)
Injection-Info: dont-email.me; posting-host="ce3eaee7b38cea081e4acffc0808b70e";
	logging-data="2192399"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19X3YbI50ppoOwyfoEzLGT6"
User-Agent: Gnus/5.13 (Gnus v5.13)
Cancel-Lock: sha1:0aJxKgU90U6eesORjSeL1vEpLw4=
	sha1:kK3RL4MGiXxYryPoO58LOQQnDK4=
Bytes: 1535

"Paul Edwards" <mutazilah@gmail.com> writes:
[...]
> With the benefit of hindsight, is there any reason why fpeek
> couldn't have been added to C90, with implementations
> being allowed with just a macro that returns some sort of
> "unsupported"?
>
> If fpeek (or similar) makes sense, can someone suggest an
> appropriate interface?
[...]

It would help to know what "fpeek" is supposed to do.  There no such
function in any edition of the C standard or in any implementation
that I'm aware of.

-- 
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
void Void(void) { Void(); } /* The recursive call of the void */