Re: preprocessing subterfuge

Article View: comp.std.c

Article #127

#127

From: Steve Clamage
Date: Mon, 10 Aug 1992 16:17

20 lines
1329 bytes

enag@ifi.uio.no (Erik Naggum) writes:

|Steve Clamage <steve@taumet.com> writes:
|>
|>   5.  In our first effort at making a Standard compiler, we rejected all
|>   non-conforming code.  We quickly found out no one would buy such a
|>   compiler.  We had to allow, at least under some circumstances, even code
|>   which was explictly illegal because our customers demanded compatibility.

|Sigh.  Where can I get a compiler which rejects non-conforming code?
|Call it an educational tool more than a production tool, if you like.

Our compilers (Oregon C/C++)  have a "strict" mode which disallows
non-conforming code.  It is not feasible (or in some cases, possible)
to detect all code which is not conforming, but we do what we can.  It
is useful for finding code with non-portable extensions or dependencies.
-- 

Steve Clamage, TauMetric Corp, steve@taumet.com
Vice Chair, ANSI C++ Committee, X3J16

Technical Details

Message-ID: <1992Aug10.161742.6181@taumet.com>

Path: arc1-ca.pugleaf.net!sparky!uunet!taumet!steve

References: <1992Aug7.001510.13418@mri.com> <MJN.92Aug9024600@pseudo.uucp> <1992Aug9.144525.4521@taumet.com> <23277A@erik.naggum.no>

Show Full Headers

Complete Article Headers

Newsgroups: comp.std.c
Path: arc1-ca.pugleaf.net!sparky!uunet!taumet!steve
From: steve@taumet.com (Steve Clamage)
Subject: Re: preprocessing subterfuge
Message-ID: <1992Aug10.161742.6181@taumet.com>
Organization: TauMetric Corporation
References: <1992Aug7.001510.13418@mri.com> <MJN.92Aug9024600@pseudo.uucp> <1992Aug9.144525.4521@taumet.com> <23277A@erik.naggum.no>
Date: Mon, 10 Aug 1992 16:17:42 GMT
Lines: 20

Reply to Parent Message