Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!decwrl!sun!pitstop!sundc!seismo!uunet!auspex!guy
From: guy@auspex.UUCP (Guy Harris)
Newsgroups: comp.lang.c
Subject: Re: AT&T C compilers
Keywords: C compiler,bug?
Message-ID: <1106@auspex.UUCP>
Date: 3 Mar 89 08:12:20 GMT
References: <569@marob.MASA.COM> <1071@auspex.UUCP> <1109@wpi.wpi.edu>
Reply-To: guy@auspex.UUCP (Guy Harris)
Organization: Auspex Systems, Santa Clara
Lines: 22

>Although AT&T still hasn't gotten its act together yet,

I think S5R4 will fully support ANSI C (assuming that "ANSI C" exists in
time to make an implementation for S5R4; otherwise, it'll probably
correspond to the last draft that AT&T could reasonably use to build an
implementation).

>ANSI prototypes are definitly worth using

Yes, I think most of us agree; however, the fact is that not all UNIX C
compilers support them, so you either have to live with that or get a
compiler such as GCC that does support them.

>Does any one know why AT&T is delaying so much?

No, perhaps they decided not to put out an "old C plus prototypes"
compiler as a stopgap measure?

>Standard UNIX C still barfs on things like p=-1 .

The System V C compiler may issue a warning, but it interprets that
statement as "assign -1 to 'p'".  It certainly doesn't "barf" on it.