Deutsch   English   Français   Italiano  
<vr7cmo$2fpma$1@dont-email.me>

View for Bookmarking (what is this?)
Look up another Usenet article

Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: James Kuyper <jameskuyper@alumni.caltech.edu>
Newsgroups: comp.lang.c
Subject: Re: __func__ is not a keyword
Date: Sun, 16 Mar 2025 16:35:36 -0400
Organization: A noiseless patient Spider
Lines: 18
Message-ID: <vr7cmo$2fpma$1@dont-email.me>
References: <vr4lgu$63fu$1@dont-email.me>
 <87bju2htxy.fsf@nosuchdomain.example.com>
 <6sCBP.1140938$t84d.713135@fx11.iad>
 <87bju0x10g.fsf@nosuchdomain.example.com> <20250316115725.530@kylheku.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Injection-Date: Sun, 16 Mar 2025 21:35:42 +0100 (CET)
Injection-Info: dont-email.me; posting-host="f0a8961278fee56e756e6248092c64be";
	logging-data="2614986"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19U/8RLQNK8A/2oPafxsahktWx8zv4vyfQ="
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:nAo/K0+bPRmO3GiZvhpTNhkURpo=
In-Reply-To: <20250316115725.530@kylheku.com>
Content-Language: en-US
Bytes: 2046

On 3/16/25 15:05, Kaz Kylheku wrote:
> On 2025-03-16, Keith Thompson <Keith.S.Thompson+u@gmail.com> wrote:
....
>> It's not a conformance issue, since __func__ is a reserved identifier
>> and any code that can tell whether it's a keyword has undefined
>> behavior.
> 
> But __func__ is not a reserved identifier!

Footnote 79 disagrees: "79) Since the name __func__ is reserved for any
use by the implementation (7.1.3), if any other identifier is explicitly
declared using the name __func__, the behavior is undefined."

Actually, I don't see how 7.1.3 applies. I think the conclusion is
correct, but the relevant citation should be 6.2.4.1p7: "All identifiers
that begin with a double underscore (__) ... are reserved for any use.
....". That wording used to be in 7.1.3. That wording was moved from
7.3.1 in n2573.pdf (2020-10-01) to 6.2.4.1 in n2596.pdf (2020-12-11).