|
From: | Paul Eggert |
Subject: | _Noreturn and draft C23 |
Date: | Mon, 27 Mar 2023 11:54:30 -0700 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0 |
Draft C23 requires [[noreturn]] before "extern" and states that _Noreturn is obsolescent. It's plausible that a future C version will drop the requirement to support the _Noreturn keyword. If that happens, "#define _Noreturn [[noreturn]]" won't be a valid workaround unless people write "_Noreturn extern" instead of "extern _Noreturn", and similarly for "_Noreturn static" etc.
Should we change Gnulib code and put _Noreturn first in its declarations now, proactively? This might help future-proof the code, and get people used to putting directives first. (But of course it would be annoying to churn in this way.)
[Prev in Thread] | Current Thread | [Next in Thread] |