Re: test in a m4 macro and variable created from pushdef

[Benoit SIGOURE <tsuna@xxxxxxxxxxxxx>]

On Aug 10, 2007, at 4:57 AM, Eric Blake wrote:

> According to Vincent Torri on 8/9/2007 12:11 PM:
> > I have another problem, which is similar. The problem is the  
> > result of
> > AM_CONDITIONAL. Here is my macro:
> >
> > AM_CONDITIONAL(BUILD_DRIVER_[]UP, test "x${use_]DOWN[}" = "xyes")
>
> Follow the quoting rule of thumb - if you don't want things expanded
> immediately, then use one level of [] per () to protect the argument
> collection scan, thereafter, use nested quotes to control how the
> expansion is parsed.  You want to make sure that UP and DOWN are
> independent tokens after the AM_CONDITIONAL is expanded, so this  
> pattern
> should do it:
>
> AM_CONDITIONAL([BUILD_DRIVER_[]UP, test "x${use_[]DOWN}" = "xyes"])

Hum, shouldn't this be:
AM_CONDITIONAL([BUILD_DRIVER_[]UP], [test "x${use_[]DOWN}" = "xyes"])
instead?

(basically s/, /], [/ ?)

--
Benoit Sigoure aka Tsuna
EPITA Research and Development Laboratory

Attachment: PGP.sig
Description: This is a digitally signed message part

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