[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: manywarnings for C++
From: |
Eric Blake |
Subject: |
Re: manywarnings for C++ |
Date: |
Mon, 7 Aug 2017 10:39:02 -0500 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 |
On 08/07/2017 10:14 AM, Reuben Thomas wrote:
> On 7 August 2017 at 16:12, Bruno Haible <address@hidden> wrote:
>
>> Reuben Thomas wrote:
>>> the ability to AC_DEFUN a
>>> macro with a particular argument, as in:
>>>
>>> AC_DEFUN([gl_UNKNOWN_WARNINGS_ARE_ERRORS(C)],
>>>
>>> so that it is possible to AC_REQUIRE such a macro.
>>
>> The '(C)' part is not an argument to the function. It's part of the
>> function name. By convention, such a function name is used to indicate the
>> implementation of an autoconf macro for a particular _AC_LANG value.
>>
>
> So how does one supply an argument? Is it
>
> gl_UNKNOWN_WARNINGS_ARE_ERRORS(C)([variable])?
Such a function can only be called indirectly (and in fact, AC_REQUIRE
is probably the best such way to call it indirectly). Autoconf's
AC_LANG magic already knows how to indirectly call several macros
defined with different language-specific mechanisms, and it looks like
this patch is adding another similar use.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
signature.asc
Description: OpenPGP digital signature
- Re: manywarnings for C++, Reuben Thomas, 2017/08/05
- Re: manywarnings for C++, Reuben Thomas, 2017/08/07
- Re: manywarnings for C++, Bruno Haible, 2017/08/07
- Re: manywarnings for C++, Reuben Thomas, 2017/08/07
- Re: manywarnings for C++, Reuben Thomas, 2017/08/07
- Re: manywarnings for C++, Reuben Thomas, 2017/08/07
- Re: manywarnings for C++, Reuben Thomas, 2017/08/07
- Re: manywarnings for C++, Bruno Haible, 2017/08/07
- Re: manywarnings for C++, Reuben Thomas, 2017/08/07
- Re: manywarnings for C++, Bruno Haible, 2017/08/07
- Re: manywarnings for C++, Reuben Thomas, 2017/08/07