Re: Moving diversions into M4sugar

[Alexandre Oliva]

On Oct 26, 2000, <address@hidden> wrote:

>> In fact, I'd go farther that way, and move some of the diversions into
>> m4sugar, some to m4sh and keep some in acgeneral.

> I don't understand ``some in m4sh'', there is really nothing related to
> it in there.

I'm talking about defining m4 diversion support and maybe some generic
diversion names into m4sugar, but moving most of the diversions that
are specific for shell-scripting to m4sh.  And then, keep some
autoconf-specific diversions in acgeneral.m4

But this can only be done properly if numbering of m4sugar diversions
doesn't conflict with that of m4sh and that of autoconf.  The simplest
way to do that is by defining macros in each layer that adjust the
numbers given as its arguments to one plus the number of the
diversions defined in the layer itself.  Then, if you add a new
diversion to m4sugar, you just have to adjust the definition of
m4sugar_new_diversion, that all diversion definitions in m4sh would
use.  Then, if you add a new diversion to m4sh, you adjust
m4sh_new_diversion, that calls m4sugar_new_diversion, and you're done.
We don't need an AC_NEW_DIVERSION, though; autoconf's diversions can
still be built atop m4sh_new_diversion

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                  address@hidden, redhat.com}
CS PhD student at IC-Unicamp        address@hidden, gnu.org}
Free Software Evangelist    *Please* write to mailing lists, not to me