Date: Mon, 16 Dec 2002 08:23:49 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: djgpp-workers AT delorie DOT com
Subject: Re: Documentation missing
In-Reply-To: <10212160150.AA21798@clio.rice.edu>
Message-ID: <Pine.SUN.3.91.1021216081951.5161H-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Sun, 15 Dec 2002, Charles Sandmann wrote:

> Many of the utilities are missing documentation.  Am I missing where
> I should look?  In particular,
>   symify, go32-v2, stubify, stubedit, exe2coff, dxegen, edebug32, fsdb

You are not missing anything, IIRC.  These are indeed undocumented.

edebug and fsdb have built-in documentation (but still need at least some 
external docs, IMHO--for example, fsdb supports a few environment 
variables that no one besides Morten knows about, unless they've read the 
entire source ;-).

The others are simply not documented.  Volunteers are welcome.  FWIW, 
documenting a small utility is a good exercise in writing Texinfo docs, 
which might come in handy if you want to do larger Texinfo jobs in the 
future.  It's good to have this in your baggage.

> These all seem like utilities, so the driver should be utils/utils.tex
> with appropriate modifications (or includes like djasm.txi).

Agreed.

> I will be doing something for dxegen.

Thanks!