Re: bug report and patch: handling of chained wrapups

[Eric Blake]

john <jbrzusto <at> fastmail.fm> writes:

> 
> Hello,
> 
> There is a bug in how GNU m4 processes text saved with m4wrap()
> once it is already using such text as input.

Thanks again for the patch; I'm now looking at it.  However, it points out that 
GNU m4 has a POSIX-compliance bug.  POSIX states: "If the m4wrap macro is used 
multiple times, the arguments specified shall be processed in the order in 
which the m4wrap macros were processed."

Solaris 8 /usr/xpg4/bin/m4 is correct:
m4wrap(a)m4wrap(b)^D
ab

But GNU m4 (1.4.4 and CVS head) is incorrectly evaluating it as:
m4wrap(a)m4wrap(b)^D
ba

We definitely need to fix the core dump, but we should also fix the broken 
semantics.

-- 
Eric Blake