Sender: rich AT phekda DOT freeserve DOT co DOT uk
Message-ID: <396B6BB3.49C1F993@phekda.freeserve.co.uk>
Date: Tue, 11 Jul 2000 19:47:15 +0100
From: Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.14 i586)
X-Accept-Language: de,fr
MIME-Version: 1.0
To: djgpp-workers AT delorie DOT com
Subject: Re: mkdoc patch, take 2
References: <Pine DOT SUN DOT 3 DOT 91 DOT 1000711100538 DOT 19180B-100000 AT is>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com

Hello.

Eli Zaretskii wrote:
> I think you are mixing two different things.  The ANSI/non-ANSI
> indication in the docs means that the relevant feature is specified in
> the ANSI Standard.

Really? I always thought "portability" meant that I could recompile my
program unchanged under another OS which supported the standards listed.
You are quite right - I am mixing things here.

> Whether our implementation complies to the letter of that specification
> is irrelevant here.  (In general, where there's no strict compliance, we
> have a bug on our hands ;-)

Are these things mentioned anywhere in the documentation? If not, perhaps
it is a good idea to add a section to the libc documentation that
describes the format of each page? Maybe some kind of introduction?

Thanks, bye,

-- 
Richard Dawe
[ mailto:richdawe AT bigfoot DOT com | http://www.bigfoot.com/~richdawe/ ]