Date: Mon, 23 Feb 1998 19:05:42 -0800 (PST)
Message-Id: <199802240305.TAA28177@adit.ap.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: George Foot <george DOT foot AT merton DOT oxford DOT ac DOT uk>
From: Nate Eldredge <eldredge AT ap DOT net>
Subject: Re: Suggestion: Portability section for libc docs
Cc: djgpp-workers AT delorie DOT com
Precedence: bulk

At 06:26  2/23/1998 +0000, George Foot wrote:

>We get back to the question: "Who is writing this information?".  The only
>information that everybody can supply is the ANSI/POSIX information, based
>upon djgpp's header files.  Other information can only be added by people
>with access to the relevant compilers.  Perhaps it would be best to begin
>by simply adding the ANSI/POSIX information, and adding the other
>information to the .txh files in a second pass, done by people with access
>to each compiler.

That is sensible. 

>Using the macros I just suggested this could be fairly simple to automate
>(search for @node <function>, then find the next @portability_end, then
>add the relevant information before that line).

The fact that the .txh files are all short helps, too.

>Perhaps we should find out how many people will be working on this fairly
>soon, though, and which systems they can compare with.

I've had offers from various people, although for many it wasn't clear
exactly how much work they'd be able to put into it. Here's a list of
volunteers and systems, however.

Me                      <eldredge AT ap DOT net>
        Linux, TC++ 1.01 :), FreeBSD 2.0.5 (4.4 BSD Lite) if necessary (I
have a         CDROM of it)

Tom Demmer              <demmer AT LSTM DOT Ruhr-UNI-Bochum DOT De>
        TC 2.0, IBM AIX

Eli                     <eliz AT is DOT elta DOT co DOT il>
        BC <= 3.1, SunOS 4.x, SunOS 5.x, Alpha/Unix, Linux

George                  <george DOT foot AT merton DOT oxford DOT ac DOT uk>
        Digital Unix/Alpha, Linux

Andrew Crabtree         <andrewc AT rosemail DOT rose DOT hp DOT com>
        HPUX 9 and 10

Cesar Scarpini Rabak    <csrabak AT dce03 DOT ipt DOT br>
        Borland C/C++ 4.5

Hopefully this will give us an idea of what we have to work with.

So I guess the next thing to do is to implement the `mkdoc' macros so we
know what to write. 

Nate Eldredge
eldredge AT ap DOT net