Sender: nate AT cartsys DOT com
Message-ID: <35C74C29.EBC9292E@cartsys.com>
Date: Tue, 04 Aug 1998 11:00:09 -0700
From: Nate Eldredge <nate AT cartsys DOT com>
MIME-Version: 1.0
To: djgpp-workers AT delorie DOT com
Subject: emu387 functions undocumented/undeclared
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Precedence: bulk

The functions in the emu387 tree of libc aren't documented, and also
aren't declared in any headers.  The major one of interest is
`_detect_80387'; there is also `_npxsetup' and a few globals.  I will
write the docs, but what header should they go in (if any)?

Also, what is the policy on documentation of functions?  libc.inf says
it documents "all public symbols", but that's not really the case.  Some
public symbols are internal to the library and completely useless to an
application.  (Examples: __crt1_startup, and the dummy
__emu387_load_hook.)  Should we document them, if only to say "internal
to libc, don't use"?
-- 

Nate Eldredge
nate AT cartsys DOT com