Date: Tue, 1 Sep 1998 11:34:17 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: George Foot <george DOT foot AT merton DOT oxford DOT ac DOT uk>
cc: djgpp-workers AT delorie DOT com
Subject: Re: Patch to mkdoc and re: portability information
In-Reply-To: <E0zDcyX-0007ul-00@sable.ox.ac.uk>
Message-ID: <Pine.SUN.3.91.980901113355.26794J-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Tue, 1 Sep 1998, George Foot wrote:

> > > Finally we need to go through the .txh files adding the information.  
> > > This is a big task, but not very difficult to do at a simple level, 
> > > since the header files already show whether a function is defined in 
> > > ANSI or POSIX or neither.
> > 
> > You could do this with a program, or even a Sed script, since the
> > __STRICT_ANSI__ and __POSIX_SOURCE symbols tell the whole story.
> 
> That might not be trivial because different nodes have different 
> amounts of documentation; some have examples, some don't, some have 
> miscellaneous notes after the return value but before the example, 
> ...  My Sed scripting isn't up to this. ;)

This was just an idea.  The person who should be *really* motivated to
do something like that is the one who gets the dubious pleasure of
creating the portability info ;-).