Re: #warning

Article View: comp.std.c++

Article #3491

#3491

From: Michael Cook
Date: Fri, 16 Feb 1996 03:54

13 lines
1163 bytes

>>>>> "SC" == Steve Clamage <clamage@Eng.Sun.COM> writes:

 SC> you forgot to say how it differs from #error

 SC> I suspect you have in mind that somehow #error would halt compilation
 SC> and #warning would not, but we don't get to talk about those things in
 SC> the standard.

Then the difference would be implementation defined.
---
[ comp.std.c++ is moderated.  Submission address: std-c++@ncar.ucar.edu.
  Contact address: std-c++-request@ncar.ucar.edu.  Moderation policy:
  http://reality.sgi.com/employees/austern_mti/std-c++/policy.html. ]

Technical Details

Message-ID: <r4hgwslcg3.fsf@erawan.cognex.com>

Path: arc1-ca.pugleaf.net!in1.uu.net!bounce-back

References: <270631188wnr@pires.co.uk> <4ftd0p$c5s@engnews1.Eng.Sun.COM>

Show Full Headers

Complete Article Headers

From: Michael Cook <mcook@cognex.com>
Message-ID: <r4hgwslcg3.fsf@erawan.cognex.com>
X-Original-Date: 15 Feb 1996 12:34:52 -0500
Path: arc1-ca.pugleaf.net!in1.uu.net!bounce-back
Date: 16 Feb 96 03:54:34 GMT
Approved: fjh@cs.mu.oz.au
Newsgroups: comp.std.c++
Subject: Re: #warning
Organization: Cognex Corporation, Natick, Massachusetts
References: <270631188wnr@pires.co.uk> <4ftd0p$c5s@engnews1.Eng.Sun.COM>
X-Newsreader: September Gnus v0.38/Emacs 19.30
X-Auth: PGPMoose V1.1 PGP comp.std.c++
 iQBFAgUBMSQAB+EDnX0m9pzZAQE7lgF9GWiR6gDKnf4F+2DfvMUZvhRRLB8fv1c5
 bQS9lJgMfPlL048QpHuRWfrCsGDY++wy
 =5PT4

Reply to Parent Message