Message-Id:	<5.0.1.4.0.20001125013858.00a5dcc0@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 01:52:54 -0500
To:	djgpp-workers AT delorie DOT com
From:	"Peter J. Farley III" <pjfarley AT banet DOT net>
Subject:	How are include/*.h headers maintained?
Mime-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com

Warning:  I have changed several wrap settings in my mail program, so 
this message may or may not wrap well.  If it does not, I will re-send 
it with (hopefully) better settings after I review how it came out in 
the mail archive.

In devising a better test for the locking fcntl() code (coming soon, 
with a corrected version of fcntl() too), I wanted to use the 
dosexterr() function to tell me what error DOS last saw, but 
dosexterr() only returns numeric values, not the string meaning of 
those values.  I developed a set of new DOS-only functions patterned 
after strerror() to produce the strings describing the four values 
returned by dosexterr().  To integrate it into the libc source tree 
properly, I believe I need to add these four functions to the 
include/dos.h header, where dosexterr() is defined.  I would propose 
putting these new functions in the libc/dos/compat directory where 
dosexterr() resides.

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?  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?

TIA for any info you can provide.

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

- Raw text -