Re: RFC: m4 2.0 --prepend-include option

[Eric Blake]

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

According to Paul Eggert on 8/23/2006 4:43 PM:
> 
>>>    3.  Whether 'define' implies 'undefine' or 'popdef'.
>>> ...
>>> For (3) perhaps we can ask POSIX to allow the GNU behavior; then
>>> we can remove the POSIXLY_CORRECT dependency.
>> Actually, for (3), I'm not even sure POSIX has an opinion one way or the
>> other - it is only the NEWS file of GNU m4 that claims that POSIX required
>> the undefine() behavior,
> 
> I just now read the POSIX spec and I agree with you: it does not
> clearly state the behavior one way or the other.  Therefore GNU m4 can
> and should do it the "right" way, regardless of POSIXLY_CORRECT.  Or,
> if you want to be more conservative about this, we can ask for a
> ruling that this is OK (I'm pretty sure the answer will be "yes" given
> the longstanding default behavior of GNU M4).

Hmm, that's not quite what we thought earlier:
http://lists.gnu.org/archive/html/m4-patches/2003-06/msg00035.html

I'll go ahead and file that aardvark.

- --
Life is short - so eat dessert first!

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

iD8DBQFE7RU984KuGfSFAYARAu8oAKCbXGAPd+Tuu4HtymtdnfVD5h3KPgCgzFhb
OZjyMnsH4zQqXZ8pL0Wk9BM=
=IYGf
-----END PGP SIGNATURE-----