Ludovic Courtès wrote:
> What would you think of sticking to the standard and less problematic
> ‘_Noreturn’ identifier in Gnulib?
That's what Gnulib does already. Other than the stdnoreturn module
itself, Gnulib modules always use _Noreturn rather than
noreturn. This is not merely because of n
Bruce Korb skribis:
> On 11/17/13 13:18, Ludovic Courtès wrote:
>> What would you think of sticking to the standard and less problematic
>> ‘_Noreturn’ identifier in Gnulib?
>>
>> (I also agree that it’s better for Guile’s public headers to use
>> ‘__noreturn__’, but using ‘noreturn’ was not comp
On 11/17/13 13:18, Ludovic Courtès wrote:
What would you think of sticking to the standard and less problematic
‘_Noreturn’ identifier in Gnulib?
(I also agree that it’s better for Guile’s public headers to use
‘__noreturn__’, but using ‘noreturn’ was not completely silly either.)
"noreturn" i
Paul Eggert skribis:
> A better solution, if you want to be portable to
> MSVC, is to use _Noreturn instead of noreturn.
> This is for reasons described in stdnoreturn.in.h.
>
> '_Noreturn' is a bit ugly; if you don't care about
> MSVC, then __attribute__((__noreturn__)) is
> a good way to go.
N
Bruce Korb writes:
> On 11/10/13 12:41, Paul Eggert wrote:
>> A better solution, if you want to be portable to
>> MSVC, is to use _Noreturn instead of noreturn.
>> This is for reasons described in stdnoreturn.in.h.
>>
>> '_Noreturn' is a bit ugly; if you don't care about
>> MSVC, then __attribute
On 11/10/13 12:41, Paul Eggert wrote:
A better solution, if you want to be portable to
MSVC, is to use _Noreturn instead of noreturn.
This is for reasons described in stdnoreturn.in.h.
'_Noreturn' is a bit ugly; if you don't care about
MSVC, then __attribute__((__noreturn__)) is
a good way to go
A better solution, if you want to be portable to
MSVC, is to use _Noreturn instead of noreturn.
This is for reasons described in stdnoreturn.in.h.
'_Noreturn' is a bit ugly; if you don't care about
MSVC, then __attribute__((__noreturn__)) is
a good way to go.
On 11/10/13 00:13, Harlan Stenn wrote:
Bruce,
I'm seeing build errors on psp-fb1 with the guile headers as well, and
autogen-5.18.2.
Errors like this:
/usr/bin/gcc-4.6 -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -I.. -I../autoopts \
-g -O2 -MT autogen-ag.o -MD -MP -MF .deps/autogen-ag.Tpo -c -o