[Top][All Lists]

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

Re: AC_C_NORETURN macro?

From: Bruno Haible
Subject: Re: AC_C_NORETURN macro?
Date: Mon, 30 Apr 2012 00:31:15 +0200
User-agent: KMail/4.7.4 (Linux/3.1.10-1.9-desktop; KDE/4.7.4; x86_64; ; )

Hi Paul,

> > The reason why we do this with explicit #ifs that test for a compiler
> > brand, not in an "Autoconfish way", is that we use the result in .h
> > files that should be installable
> That makes sense for the definition of _Noreturn in
> build-aux/snippet/_Noreturn.h, since that file is
> copied into installable .h files.  But it makes less
> sense for the common Autoconf situation where _Noreturn
> is defined in <config.h>; such definitions are not intended
> to be copied into installable .h files, and it might make
> sense for Autoconf to support that.

Currently gnulib covers both use-cases well:
  - use of _Noreturn in source files of the same package that don't
    include <stdnoreturn.h>,
  - use of 'noreturn' in installable .h files.
This is because we put the same snippet both into m4/gnulib-common.m4
(from where it goes to config.h) and into a build-aux/snippets/ file
(from where it gets copied into the installable .h file).

What kind of service from Autoconf, do you imagine, could help or simplify


reply via email to

[Prev in Thread] Current Thread [Next in Thread]