Re: AC_C_NORETURN macro?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 2012-04-26 12:08:50 -0400, Nick Bowler wrote:
> On 2012-04-26 17:56 +0200, Vincent Lefevre wrote:
> > But I think that <stdnoreturn.h> is not a solution for MPFR, due to
> > the potential clashes with GMP (on which we depend), which uses GCC's
> > __attribute__ ((noreturn)). Though this may be fixed in the future,
> > problems would still appear with older versions. Thus we should use
> > _Noreturn directly, when supported.
> 
> Another alternative is to simply make sure that you always include the
> GMP headers before including <stdnoreturn.h>.

Perhaps. But GMP requires some standard headers, like <stdio.h>
to be included before in order to use some functions. With all
constraints like that, this makes things less maintainable. And
there may be buggy C implementations, where some headers may
include other ones without enough guards. I've already seen that.

-- 
Vincent Lefèvre <vincent@xxxxxxxxxx> - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
https://lists.gnu.org/mailman/listinfo/autoconf



[Index of Archives]     [GCC Help]     [Kernel Discussion]     [RPM Discussion]     [Red Hat Development]     [Yosemite News]     [Linux USB]     [Samba]

  Powered by Linux