[Top][All Lists]

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

Re: use of AC_TRY_EVAL broken

From: Bruno Haible
Subject: Re: use of AC_TRY_EVAL broken
Date: Sun, 2 Nov 2008 19:38:16 +0100
User-agent: KMail/1.5.4

Hi Eric,

> What if we create and document the following macro names:
> AC_COMMAND_IFELSE(command with args, if-true, if-false)
> AC_EVAL_IFELSE(variable, if-true, if-false)
> where AC_EVAL_IFELSE([variable]) is shorthand for AC_COMMAND_IFELSE([eval
> "$variable"])?  Does that solve the immediate need?

Sounds good.

Should the arguments support double-quoting or only single-quoting? I.e. if
there is a macro LT_LINK_COMMAND which expands into a command with arguments
(possibly containing commas), should the user then write

And what do you plan to do regarding ac_link and ac_compile, which are
currently undocumented?


reply via email to

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