Path: csiph.com!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: Tim Rentsch <tr.17687@z991.linuxsc.com>
Newsgroups: comp.std.c
Subject: Re: Invalid sample definition for errno
Date: Sun, 20 Nov 2022 05:26:40 -0800
Organization: A noiseless patient Spider
Lines: 14
Message-ID: <86sfidbvu7.fsf@linuxsc.com>
References: <87r0xyl6nm.fsf@nosuchdomain.example.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Injection-Info: reader01.eternal-september.org; posting-host="a724f5b4ee1d34e760f89c516bf20c9c"; logging-data="3707309"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18hq+1sDxOG7b1HDH4SrnWse70/jlM7qVU="
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.4 (gnu/linux)
Cancel-Lock: sha1:fF6s1XfIVeEWXOCEg8kxY0UXKIY= sha1:2yBnZEF+2pOv+YKixHVM9WHmU8s=
Xref: csiph.com comp.std.c:6452

Keith Thompson <Keith.S.Thompson+u@gmail.com> writes:

> A footnote in the section describing <errno.h> says:
>
>     The macro errno need not be the identifier of an object.  It might
>     expand to a modifiable lvalue resulting from a function call (for
>     example, *errno()).
>
> Footnotes are non-normative, and this one is presumably intended to be
> informal, but that's not a valid macro definition for errno, both
> because it's not fully protected by parentheses and because the function
> can't be named "errno".

I see no reason the function couldn't be named "errno".