Date: Wed, 11 Feb 1998 20:56:16 -0500 (EST)
Message-Id: <199802120156.UAA17898@delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: djgpp-workers AT delorie DOT com
In-reply-to: <Pine.OSF.3.95.980211220812.22819C-100000@sable.ox.ac.uk>
	(message from George Foot on Wed, 11 Feb 1998 22:35:58 +0000 (GMT))
Subject: Re: Suggestion: Portability section for libc docs
Precedence: bulk


> If it's too much work to do that initially, we could make a start by
> classifying each function ANSI/POSIX/neither, and add more details later
> on.

Since we parse the txi files anyway, we can use macros to denote
compatibility and turn them into texinfo when we run mkdoc.  This
would make maintenance a lot easier and keep the texts consistent.
For example:

	@compat posix ansi -bc msvc20
		posix and ansi, not in borland, only in msvc 2.0+

	@compat ansi stub
		ansi, but it's only a stub - doesn't really do anything

	@compat ~posix ansi
		sort of posix (prototype right, some functional differences)
		but meets ansi spec

> I suggest we take the alphabetical listing and divide it up between the
> volunteers.  Each volunteer can add the basic information for each

How about by source directory instead?  That's easier to work with in
the source tree, which is where the txi files are.