Mail Archives: djgpp-workers/2003/02/10/07:41:44
On Fri, 7 Feb 2003, Richard Dawe wrote:
> 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?
[snip]
> It just seems like overkill to have mkdoc do all this stuff, when texinfo
> already has @include.
Overkill it may be, but I really think that mkdoc would be more
complicated if it had to output another file to pass to texinfo,
compared to the case where mkdoc puts everything it processes into a
single file.
> It sounds like you want mkdoc to become a much more
> feature-full pre-processor.
Yes, that's more or less right. (Though I think I'll finish the
stack-checking thing first.)
> 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?
If that were feasible, we could just use findutils to find the files. :-)
--
Esa Peuha
student of mathematics at the University of Helsinki
http://www.helsinki.fi/~peuha/
- Raw text -