| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org |
| Cc: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Subject: | Re: pg_attribute_noreturn(), MSVC, C11 |
| Date: | 2024-12-14 17:18:35 |
| Message-ID: | 00f91261-5e2d-4553-9b18-ade7e3a484ab@eisentraut.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 13.12.24 20:54, Andres Freund wrote:
> Another wrinkle: While __attribute__((noreturn)) works for function pointers
> (or function pointer typedefs) _Noreturn doesn't. Gah. We only use it that
> way in two places, but still :(
Yeah, I wrote an experimental patch for noreturn support some years ago,
and that was also my result back then. (I assume you have a current
patch, otherwise I can dig out that one.) I had also written down that
there were some problems with Perl and Tcl headers, FWIW. Did you have
any problems with those?
I think we can take a small loss here and move with the standard.
Unless you can think of a way to define
pg_noreturn_but_for_function_pointers in a systematic way.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2024-12-14 17:23:45 | Re: "collation" or "collation oder" |
| Previous Message | Peter Eisentraut | 2024-12-14 17:15:13 | Re: pg_attribute_noreturn(), MSVC, C11 |