Xref: utzoo comp.lang.c:33233 comp.std.c:3831
Path: utzoo!attcan!uunet!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!uflorida!haven!adm!smoke!gwyn
From: gwyn@smoke.brl.mil (Doug Gwyn)
Newsgroups: comp.lang.c,comp.std.c
Subject: Re: Tentative specification for UNIX Version 7 C
Message-ID: <14270@smoke.brl.mil>
Date: 29 Oct 90 00:59:25 GMT
References: <2442.272704b8@verifone.com> <1990Oct27.230447.5456@zoo.toronto.edu>
Followup-To: comp.lang.c
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 20

In article <1990Oct27.230447.5456@zoo.toronto.edu> henry@zoo.toronto.edu (Henry Spencer) writes:
>`signed char' is particularly odd, since as far as I know `signed' was
>an X3J11 invention and there were *no* pre-ANSI compilers featuring it.

Actually, there was existing practice here (Whitesmiths).

I agree with your comments about the impracticality of attempting to
define a "UNIX Version 7 C standard".  Having maintained versions of
BOTH 7th Edition UNIX C compilers, I can add that even the genuine
article came in two not entirely equivalent flavors.  X3J11 took the
UNIX C reference manual (essentially an update to K&R 1st Edition
Appendix A) as the language base document for the eventual C standard.
Changes and additions made during this process were the result of
trying to accommodate important real-world concerns that any such
standard should have addressed.  Anyone who thinks that he can do
better working on his own must be woefully ignorant of the issues
involved.  A large number of the world's most experienced experts in
the use and implementation of the C programming language have finally
produced the first genuine, officially sanctioned standard for C; use
it and be happy.