Re: pre-processing

[Daniel J. <dan...@gm...>]

> I am pretty sure we can assume C99 when building CLISP.

That's good :)

> * gctrigger is necessary for GCSAFETY -- keep it!

Hm ... what about this:

MAYGC(void, my_function_name, type1, param1, type2, param2) {
  // code
}

I'm pretty sure I could write a preprocessor macro that can turn the
above into the equivalent of what's currently produced by gctrigger.
(all it does is placing GCTRIGGER(param1, param2) in there,
depending on type1 and type2, right?)

Getting rid of all preprocessing would be nice because then we could
use the implicit rules and dependency tracking of automake.


> * txt2c is for doc processing, I think we should move away from it
>  (what do other projects use?)

Do I understand correctly that txt2c is mostly used to enable or
disable parts of the docs depending on the configuration, as well as
putting some data about the build and configuration into the docs
(like whether it uses trivialmap memory or not)?

This is what AC_CONFIG_FILES and its variable substitution is IMO for,
though I'm not sure if it can replace txt2c completely (and in an
elegant and easy to use way).


> I would like that to happen _after_ the release.

Sounds reasonable :)