On 04/28/2017 09:40 AM, Bruno Haible wrote:
You have been thinking of this?
#define _GL_NORETURN_FUNC_Noreturn
#define _GL_NORETURN_FUNCPTR _Noreturn __attribute__ ((__noreturn__))
It was more like this:
#define _GL_NORETURN_FUNC_Noreturn __attribute_noreturn__
#define _GL_NO
> You have been thinking of this?
> #define _GL_NORETURN_FUNC_Noreturn
> #define _GL_NORETURN_FUNCPTR _Noreturn __attribute__ ((__noreturn__))
This approach does not work:
===
void func1 (void) { for (;;); }
_Nore
Hi Paul,
> I thought we had established that in some cases one should apply both
> _Noreturn and __attribute__ ((__noreturn__)) to the same declaration? I
> don't see that in this module.
Apparently we've been thinking at different solutions of the clang problem
(which, for type checking / assi
Building the an updated version of liblouis with Ubuntu 16.10 LTS
i686-w64-mingw32-gcc fails:
i686-w64-mingw32-gcc -DHAVE_CONFIG_H -I. -I../liblouis -I../liblouis
-I../tools/gnulib -I../tools/gnulib -g -O2 -Wl,--add-stdcall-alias -MT
lou_allround.o -MD -MP -MF .deps/lou_allround.Tpo -c
I thought we had established that in some cases one should apply both
_Noreturn and __attribute__ ((__noreturn__)) to the same declaration? I
don't see that in this module.
Also, I hope we're not envisioning a lot of replacement of _Noreturn
with _GL_NORETURN_FUNC in other modules. As I unders
