Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: "Chris M. Thomasson" Newsgroups: comp.lang.c Subject: Re: Casting the return value of ... Date: Thu, 28 Mar 2024 14:15:54 -0700 Organization: A noiseless patient Spider Lines: 44 Message-ID: References: <20240328105203.773@kylheku.com> <87frwatadu.fsf@nosuchdomain.example.com> <87bk6yt68v.fsf@nosuchdomain.example.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Date: Thu, 28 Mar 2024 21:15:54 +0100 (CET) Injection-Info: dont-email.me; posting-host="77631ed3707533fd72697cf232be3393"; logging-data="4011416"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/RKiO7Y/b6zXrBWvVa4Djp9P12Fqxxvdk=" User-Agent: Mozilla Thunderbird Cancel-Lock: sha1:RaOTc2L22tsIa2RC/18A5AHwf0Y= In-Reply-To: <87bk6yt68v.fsf@nosuchdomain.example.com> Content-Language: en-US Bytes: 2891 On 3/28/2024 2:07 PM, Keith Thompson wrote: > bart writes: >> On 28/03/2024 19:38, Keith Thompson wrote: >>> Kaz Kylheku <433-929-6894@kylheku.com> writes: >>> [...] >>>> Conversions between function pointers and data pointers are an >>>> extension; it is not well-defined behavior in ISO C. >>>> >>>> Therefore we can neither say that ISO C doesn't require a cast there (it >>>> imposes no requirements at all), nor that the conversion is fine with a >>>> cast. >>>> >>>> The cast is /likely/ necessary, in order to correctly trigger the >>>> extension. >>> ISO C does require a cast. The cast is necessary to avoid a >>> constraint violation and a mandatory diagnostic. The resulting >>> behavior is undefined in ISO C, but defined by POSIX. Assigning a >>> void* value to a pointer-to-function object without a cast violates >>> the constraint for simple assignment (N1570 6.5.16.1p1). >> >> What would such a cast look like? Since this gives a warning with >> -Wpedantic even with a cast: >> >> void* p; >> void(*q)(void); >> >> p=(void*)q; >> q=(void(*)(void))p; > > The warnings I get from gcc are: > > warning: ISO C forbids conversion of function pointer to object pointer type [-Wpedantic] > warning: ISO C forbids conversion of object pointer to function pointer type [-Wpedantic] > > With -pedantic-errors, these become fatal errors. > > I disagree with gcc. ISO C doesn't define the behavior, but it doesn't > forbid the conversion. (Anyone who disagrees is invited to cite the > constraint that it violates.) > > Note that clang doesn't issue this diagnostic. > Casting might prevent a warning in certain compilers...