Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!dimacs.rutgers.edu!mips!gumby
From: sah@gumby (Steve Hanson)
Newsgroups: comp.sys.mips
Subject: Re: prototypes in the C compiler
Message-ID: <43227@mips.mips.COM>
Date: 15 Nov 90 00:36:02 GMT
References: <7031@hub.ucsb.edu> <42950@mips.mips.COM> <1132@dg.dg.com>
Sender: news@mips.COM
Reply-To: sah@gumby (Steve Hanson)
Distribution: comp
Organization: MIPS Computer Systems, Sunnyvale CA
Lines: 27
In-reply-to: lewine@cheshirecat.rtp.dg.com (Donald Lewine)

In article <1132@dg.dg.com>, lewine@cheshirecat (Donald Lewine) writes:
>Will it conform to the full ANSI Standard?  This is now an approved
>national standard.
>
>--------------------------------------------------------------------
>Donald A. Lewine                (508) 870-9008 Voice
>Data General Corporation        (508) 366-0750 FAX
>4400 Computer Drive. MS D112A
>Westboro, MA 01580  U.S.A.
>
>uucp: uunet!dg!lewine   Internet: lewine@cheshirecat.webo.dg.com



2.20 compliance will limited to a "freestanding implementation" which
accepts any strictly conforming program that confines its use of library 
features to the contents of the standard headers float.h, limits.h,
stdarg.h, and stddef.h. This is to say that for 2.20 libraries and header
files will not be ANSI'fied, however the following 3.0 release that will
be combined with RISC/os 5.0 will provide a "hosted implementation" containing
ANSI'fied libraries and headers. We do plan on going through formal validation 
with the US NIST ANSI C suite when its available. The test suite is currently
scheduled to be out of the review stage January 7.
-- 
-- 
UUCP: {ames,decwrl,prls,pyramid}!mips!sah
USPS: MIPS Computer Systems, 930 Arques Ave, Sunnyvale CA, 94086