[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: traces output order
From: |
Ralf Wildenhues |
Subject: |
Re: traces output order |
Date: |
Fri, 21 Mar 2008 08:18:00 +0100 |
User-agent: |
Mutt/1.5.17+20080114 (2008-01-14) |
* Eric Blake wrote on Fri, Mar 21, 2008 at 03:23:07AM CET:
>
> Primarily? Always! M4 traces are output in the order encountered (but
> note that nested macros are traced during argument collection, prior to
> the trace of the macro they are feeding).
Hmm. That means my current AM_COND_IF patch will treat
AM_COND_IF([OUTER],
[$outer_action
AM_COND_IF([INNER],
[$inner_action])])
correctly but mistreat
AM_COND_IF([OUTER],
$outer_action
AM_COND_IF([INNER],
[$inner_action]))
That's a bit ugly, and certainly deserves mention.
> Speaking of traces, there's a TODO mentioned in the autoconf sources that
> m4 can't trace macros called via 'indir'. I've fixed it in the argv_ref
> branch of m4.
Cool.
Happy Easter,
Ralf