-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Ralf Wildenhues on 8/14/2008 12:39 PM: >> For example, is my new macro m4_foreach_pair worth documenting as a >> supported >> interface, or should I leave it undocumented? > > How about documenting it after 2.63, so we can change it until the next > version if we find issues with it?
Sure. > >> Also, should it be named slightly differently since it behaves more >> like m4_map than m4_foreach? > > m4_map_pair maybe? I went with the name m4_transform_pair, since it turned out to be very easy to add m4_transform with similar semantics but visiting one argument at a time. In terms of macro invocations, m4_transform([func], [arg1], ...) is more efficient (and less typing) than the identical output of m4_foreach([var], [[arg1], ...], [func(m4_defn([var]))]) - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -----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 iEYEARECAAYFAkilBHMACgkQ84KuGfSFAYAK0ACfXKT4AcEo1vz9Pt11zzNoTZSu RiYAoNGJnTF+WhtSeVBM7kL5dG2Q1+QG =41Xh -----END PGP SIGNATURE-----
