Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site ut-sally.UUCP
Path: utzoo!linus!gatech!seismo!ut-sally!std-unix
From: std-unix@ut-sally.UUCP (Moderator, John Quarterman)
Newsgroups: mod.std.unix
Subject: Draft ambiguity
Message-ID: <3532@ut-sally.UUCP>
Date: Fri, 15-Nov-85 19:43:07 EST
Article-I.D.: ut-sally.3532
Posted: Fri Nov 15 19:43:07 1985
Date-Received: Sat, 16-Nov-85 03:57:58 EST
Organization: IEEE/P1003 Portable Operating System Environment Committee
Lines: 18
Approved: jsq@ut-sally.UUCP

Date:     Fri, 15 Nov 85 11:53:55 EST
From: Dan Franklin <dan@BBN-PROPHET.ARPA>

Some of the values in the column "Minimum value" are actually maximums rather
than minimums, and the draft should indicate this.  That is, for the minimums
CHAR_MIN, INT_MIN, LONG_MIN, and SHRT_MIN, the column gives the maximum
permissible value (as it should), not the minimum permissible.  Before I
realized this, I thought it was an error that the "minimum value" for CHAR_MIN
was 0 rather than -128.  One way to make this clearer would be to change the
column label "Minimum value" to "Minimum (Maximum) value" and put the values
which are actually "largest permissible minimums" rather than "smallest
permissible maximums" in parentheses.

	Dan

[ This comes up at every meeting.  Your method looks as good as any.  -mod ]

Volume-Number: Volume 3, Number 23