> But you want to divide it out:
>
> m4sugar (no quadrigraph support)
> autom4te (quadrigraphs, warnings)
> m4sh (shell functionality)
> other layers
More precisely:
m4sugar (cool stuff, supporting but not needing quadrigraphs)
autom4te (quadrigraphs, warnings)
m4sh (shell functionality)
other
Paolo Bonzini gnu.org> writes:
>
> Eric Blake wrote:
> > Paolo Bonzini gnu.org> writes:
> >
> >> m4_text_box is the sole user of quadrigraphs in m4sugar.m4.
> >
> > Nope. m4_text_wrap also uses it.
>
> m4_text_wrap knows about quadrigraphs (via m4_qlen), but does not emit
> them. If the in
Eric Blake wrote:
> Paolo Bonzini gnu.org> writes:
>
>> m4_text_box is the sole user of quadrigraphs in m4sugar.m4.
>
> Nope. m4_text_wrap also uses it.
m4_text_wrap knows about quadrigraphs (via m4_qlen), but does not emit
them. If the input has no quadrigraphs, *and does not use m4_text_box
Paolo Bonzini gnu.org> writes:
> m4_text_box is the sole user of quadrigraphs in m4sugar.m4.
Nope. m4_text_wrap also uses it.
> Together
> with m4_warn, in turn, it is the sole feature needing autom4te.
True; autom4te is mainly for quadrigraph, warning, and trace post-processing.
> I don't
m4_text_box is the sole user of quadrigraphs in m4sugar.m4. Together
with m4_warn, in turn, it is the sole feature needing autom4te. I don't
care about m4_warn very much, but it would be nice to rename m4_text_box
to AS_TEXT_BOX and move it to m4sh.
Bison does not use it, and Google says it is u
