Message-Id: <5.0.1.4.0.20001125115139.025922a0@pop5.banet.net>
X-Sender: usbanet DOT farley3 AT pop5 DOT banet DOT net
X-Mailer: QUALCOMM Windows Eudora Version 5.0.1
Date: Sat, 25 Nov 2000 11:54:49 -0500
To: djgpp-workers AT delorie DOT com
From: "Peter J. Farley III" <pjfarley AT banet DOT net>
Subject: Re: How are include/*.h headers maintained?
In-Reply-To: <3A1FE6A0.1D61685B@softhome.net>
References: <5 DOT 0 DOT 1 DOT 4 DOT 0 DOT 20001125013858 DOT 00a5dcc0 AT pop5 DOT banet DOT net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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

At 05:19 PM 11/25/00 +0100, Laurynas Biveinis wrote:
 >"Peter J. Farley III" wrote:
 >>Is the correct way to change include/dos.h to directly modify it, or 

 >>is there an automated process that maintains it from some other
 >>source?
 >
 >Modify it directly - just add prototypes to the header files. And pay
 >attention to what section new functions belong to (ANSI, POSIX,
 >everything else).

Will do, thanks.

 >> I
 >> also realize that I must write a *.txh file to document the new
 >> functions, but it looks to me like those are just for 
documentation,
 >> not for building *.h files.  Am I right about that also?
 >
 >Right.

Thanks for the confirmation, Laurynas.  It's always nice to find out 
you're seeing what's really there.

Bye for now.
---------------------------------------------------------
Peter J. Farley III (pjfarley AT dorsai DOT org OR
                      pjfarley AT banet DOT net)