Re: m4_chomp [was: Use newer m4_map_args_{w,sep}]

[Eric Blake]

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

According to Paolo Bonzini on 11/14/2008 7:49 AM:
>> argument), to mirror m4_esyscmd/m4_esyscmd_s?  On the other hand, the user
>> can supply @&t@ if that trailing newline is important, so maybe making
>> m4_expand always supply/strip an extra newline is the way to go?
> 
> I obviously prefer the latter... but why don't you instead simply make
> chomp delete only *one* newline?

What if the user does:

m4_expand([
dnl])

Stripping one newline just did the wrong thing.  As long as we are at risk
of doing it wrong by stripping one, it is just as easy to strip them all.
 And in the case of m4_esyscmd_s, you actually want to strip all newlines,
to match `` behavior.  But yes, limiting to one newline is as easy as
changing the regexp in m4_chomp from /*$ to /?$.

- --
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

iEYEARECAAYFAkkdk9gACgkQ84KuGfSFAYBsIQCgk4Z0IuorpaqMzKCxGH5Y+Ndw
k3MAoM7JK9JWN5wFMUzUZqEjTSkiI3/n
=EpgG
-----END PGP SIGNATURE-----