-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Ralf Wildenhues on 3/25/2008 5:14 PM: |> On Fri, March 21, 2008 14:02, Eric Blake wrote: |>> Ralf Wildenhues <Ralf.Wildenhues <at> gmx.de> writes: | |>>> + _AM_COND_IF => 1, |>>> + _AM_COND_ELSE => 1, |>>> + _AM_COND_ENDIF => 1, |>> Based on your question about trace order, should this section be modified |>> to take macro invocation depth into account to work around underquoted |>> usage? | | Well, I guess the cheapest way to cope with underquoted usage is to | error out when the macro depth is not 1, right?
I hadn't thought about that option, but it sounds acceptable to me. But make sure it's documented - automake is imposing a restriction above and beyond what m4 can normally do (and that's only because autom4te trace output is post-processed; there's no way in m4 to directly learn current nesting level). | | WDYT? Looks okay from my perspective. | + | [EMAIL PROTECTED] macros may be nested. Maybe add a line here about needing proper quoting to do nesting? - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -----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 iEYEARECAAYFAkfppyYACgkQ84KuGfSFAYDFtwCgjDPUIBvUAcGeoYdb5OZgVIH5 /pAAoNZwibU81W3f+khTmi9VfvM4JAlZ =yp9+ -----END PGP SIGNATURE-----
