Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!tdatirv!sarima
From: sarima@tdatirv.UUCP (Stanley Friesen)
Newsgroups: comp.lang.c++
Subject: Re: 64 bit architectures and C/C++
Message-ID: <238@tdatirv.UUCP>
Date: 3 May 91 17:42:17 GMT
References: <168@shasta.Stanford.EDU> <6157@trantor.harris-atd.com> <2110@talos.npri.com> <1991May1.222505.81@ux1.cso.uiuc.edu> <699@taumet.com>
Reply-To: sarima@tdatirv.UUCP (Stanley Friesen)
Organization: Teradata Corp., Irvine
Lines: 14

In article <699@taumet.com> steve@taumet.com (Stephen Clamage) writes:
>phil@ux1.cso.uiuc.edu (Phil Howard KA9WGN) writes:
>Some compilers already do this.  For example, our compilers (available from
>Oregon Software) have a "compatibility" switch which allows compilation of
>old-style code, including old-style preprocessing.

So does the System V release 4 compiler.  It has *three* switch setting.
An 'old code' mode that compiles old style C but complains about non-ANSI
code.  A hybrid mode which mostly compiles ANSI C, but still accepts non-
conflicting old-style stuff, and a *srict* ANSI mode, that enforces pure
ANSI compliance.
-- 
---------------
uunet!tdatirv!sarima				(Stanley Friesen)