From:	Robert Hoehne <Robert DOT Hoehne AT Mathematik DOT tu-chemnitz DOT de>
Newsgroups:	comp.os.msdos.djgpp
Subject:	To the INFO questions related to RHIDE
Date:	Fri, 14 Mar 1997 13:05:10 +0100
Organization:	TU Chemnitz-Zwickau
Lines:	41
Message-ID:	<33293EF6.6CF3@Mathematik.tu-chemnitz.de>
NNTP-Posting-Host:	errno.hrz.tu-chemnitz.de
Mime-Version:	1.0
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Here my thoughts about the two thread to that topic:

RHIDE should be used as a programming tool and not
for writing docs.
I don't know if you have ever looked a little bit deeper
at the size of rhide.exe, but you will see, that the
size is still over 1MB (uncompressed, because the rhide.exe
in the binary distrib is compressed already with DJP). 

And if I integrate more and more such features in it,
it will become sometimes a size of over 2MB and should
it realy the goal of RHIDE to implement there all the
functionallity of emacs, which can do that as far as
I remember?

And now some hints for writing the doc for functions
and/or modifying INFO files.

For modifying existing INFO-source files, you can use
any text editor (of course also RHIDE like I do for
the RHIDE doc). To create the INFO file, you should use
makeinfo.

To the doc for the functions: I saw at least in the 
sources for binutils 2.7 a good methode how it can
be solved. There is the so called 'docstrip' utility,
which scans your source files for special imbedded
comments and formats them to produce a vaild texinfo
file. Why not using that for writing the doc to all
of your functions? (This needs of course some time
to learn a little bit about the used syntax of
that tool).

Robert
-- 
*****************************************************************
* Robert Hoehne, Fakultaet fuer Mathematik, TU-Chemnitz-Zwickau *
* Post:    Am Berg 3, D-09573 Dittmannsdorf                     *
* e-Mail:  Robert DOT Hoehne AT Mathematik DOT TU-Chemnitz DOT DE              *
* WWW:     http://www.tu-chemnitz.de/~rho                       *
*****************************************************************

- Raw text -