Re: 2.62 AT_SETUP limitations

[Eric Blake]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Noah Misch on 4/22/2008 6:54 PM:
|
| How about this?  Keep the parentheses around for space preservation, but
make
| them part of a more complex quote string.

Looks like it should work - in m4_expand, the () appear as balanced
parens, but in _m4_expand, they are embedded as part of the longer quote
strings.  Thanks for the idea!  However, I'd be a bit more comfortable
adjusting m4_expand and _m4_split to use the same unlikely quotes, so we
aren't doubling our chances of the user actually clashing with it; I'll
probably check in something that uses -=<{( and )}>=- as the quote strings
across both macros.

I think that the addition of quadrigraphs for ( and ) is still useful for
corner cases, independent of improving m4_expand, so I won't back out that
change unless anyone speaks up.

- --
Don't work too hard, make some time for fun as well!

Eric Blake             address@hidden
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkgOvlcACgkQ84KuGfSFAYAtNgCaA7U/HkGWnNWx5hKqDs1bR767
5SoAn0VaTA8WxLy4uYrbaQAlyznVXHhp
=DRMD
-----END PGP SIGNATURE-----