Path: utzoo!utstat!helios.physics.utoronto.ca!jarvis.csri.toronto.edu!mailrus!shadooby!samsung!cs.utexas.edu!usc!dianne.usc.edu!blarson
From: blarson@dianne.usc.edu (bob larson)
Newsgroups: news.software.b
Subject: Cnews vs. ANSI C (was Re: Cnews and gcc 1.36 on UNIXPC)
Message-ID: <21546@usc.edu>
Date: 2 Dec 89 21:45:30 GMT
References: <1989Dec2.022346.436@ivucsb.sba.ca.us> <89Dec2.021206est.2151@neat.cs.toronto.edu>
Sender: news@usc.edu
Reply-To: blarson@dianne.usc.edu (bob larson)
Organization: USC AIS, Los Angeles
Lines: 18

In article <89Dec2.021206est.2151@neat.cs.toronto.edu> moraes@cs.toronto.edu (Mark Moraes) writes:
>[Geoff Collyer also warns that you had better use gcc -traditional --
> he staunchly denies that C News is written in ANSI C, and insists
> that compiling C News with an ANSI C compiler (alleged or otherwise)
> will void your warranty...]

Does this mean than C news won't work on a C compiler without the
"traditional" bugs, (such as using comments as token pasting, and
substituting macro paramaters in quoted strings) or just that it
doesn't take advantage of the new features in ANSI C.  If the former,
it means I have a bigger job in front of me, I'm contemplating porting
C news to os9/68k, which has a C compiler that doesn't have these
bugs.  (ANSI version will be done, but isn't yet available.)
(Yes, I realize this means translating all the shell scripts to C.)

Bob Larson	blarson@dianne.usc.edu		usc!dianne!blarson
--**		To join Prime computer mailing list		**---
info-prime-request@ais1.usc.edu		usc!ais1!info-prime-request