-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Ralf, According to Ralf Wildenhues on 3/21/2008 1:18 AM: | Hmm. That means my current AM_COND_IF patch will treat | | AM_COND_IF([OUTER], | [$outer_action | AM_COND_IF([INNER], | [$inner_action])]) Look at autom4te.cache/traces.?, with lines like: m4trace:configure.ac:3: -1- AM_COND_IF([OUTER], [$o AM_COND_IF([INNER], [$i])]) m4trace:configure.ac:3: -1- AM_COND_IF([INNER], [$i]) | | correctly but mistreat | | AM_COND_IF([OUTER], | $outer_action | AM_COND_IF([INNER], | [$inner_action])) m4trace:configure.ac:5: -2- AM_COND_IF([INNER], [$i]) m4trace:configure.ac:3: -1- AM_COND_IF([OUTER], [$o ...]) | | That's a bit ugly, and certainly deserves mention. I think I see a way around the problem. Use the nesting level, which is also part of the trace. For example, autoconf --trace=_AM_COND_IF:'$n-$d' can tell you that _AM_COND_IF-2 was probably invoked unquoted within _AM_COND_IF-1. For more assurance, you can also start looking at line numbers in the trace to ensure that the subsequent _AM_COND_IF-1 occurs on the same or earlier line than _AM_COND_IF-2, rather than the _AM_COND_IF-2 being nested in an unrelated macro call. Hmm. --trace=MACRO is documented in autoconf/autom4te --help, but not - --trace=MACRO[:FORMAT]. Should we document that in more than the manual? | Happy Easter, Same to you. - -- Don't work too hard, make some time for fun as well! Eric Blake ebb9@xxxxxxx -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkfjp/UACgkQ84KuGfSFAYDDXgCgwetjA+DRwcCnl4A3XhDsFZE2 pGUAoJMWJHytp9HCjz+rIScxbgAU4yFW =yVpO -----END PGP SIGNATURE----- _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
