Mail Archives: djgpp-workers/2003/02/07/10:21:24
Esa A E Peuha wrote:
> On Thu, 6 Feb 2003, Richard Dawe wrote:
> > Another solution to problem (a) is to get mkdoc to do the hard work. mkdoc
> > could generate a file containing all the -I options.
> Why not simply have mkdoc do the inclusion itself? After all, even now
> mkdoc reads all the .txh files into memory first and only then dumps
> them to libc2.tex; it would be quite easy to make it dump pieces of text
> more than once. And I'd also like mkdoc to read libc.tex and actually
> output one single Texinfo file which neither includes other files nor is
> included by other files; then it would be easier to use mkdoc for
> utils.info as well as libc.info.
It just seems like overkill to have mkdoc do all this stuff, when texinfo
already has @include. It sounds like you want mkdoc to become a much more
feature-full pre-processor. If that's the case, why don't we split mkdoc into
two: a program to find all .txh and some m4 macros to do the pre-processing?
(Clearly this suggestion won't fly, because it would force another tool
requirement on the build process.)
Bye, Rich =]
Richard Dawe [ http://www.phekda.freeserve.co.uk/richdawe/ ]
- Raw text -