Article View: comp.std.c++
Article #2873Re: Standard C++ Macro
From: Chris Dearlove
Date: Thu, 07 Dec 1995 16:00
Date: Thu, 07 Dec 1995 16:00
24 lines
1649 bytes
1649 bytes
Jerry Coffin (jcoffin@rmii.com) wrote: : Sean A Corfield <sean@corf.demon.co.uk> wrote: : >Interestingly (or not) there's nothing to prevent a NON-conforming C : >compiler from predefining __STDC__ to be 1! I recall a well-known compiler : >which predefined __STDC__ as zero (unless in ansi compliant mode) -- this : >wreaked havoc with code that simply had: : It's a tautology that the standard has no control over non-standard : compilers... Whilst not disagreeing with you about the actual position I have wondered before whether ANSI could have trademarked something like __STDC__ and then licensed its general use to vendors who made a reasonable atempt to be compliant. Mind you even if legal this could and I guess would) have caused more problems than it solved, especially if use required payment. -- Personal opinion only. [ comp.std.c++ is moderated. Submission address: std-c++@ncar.ucar.edu. Contact address: std-c++-request@ncar.ucar.edu. The moderation policy is summarized in http://dogbert.lbl.gov/~matt/std-c++/policy.html. ]
Technical Details
Message-ID:
<4a6s5s$4l9@miranda.gmrc.gecm.com>Path:
arc1-ca.pugleaf.net!engnews1.Eng.Sun.COM!taumet!clamageReferences:
<49kois$gqr@engnews1.eng.sun.com> <49m4kj$d6v@natasha.rmii.com>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!engnews1.Eng.Sun.COM!taumet!clamage From: chris.dearlove@gecm.com (Chris Dearlove) Newsgroups: comp.std.c++ Subject: Re: Standard C++ Macro Date: 7 Dec 1995 16:00:06 GMT Organization: ? Approved: clamage@eng.sun.com (comp.std.c++) Message-ID: <4a6s5s$4l9@miranda.gmrc.gecm.com> References: <49kois$gqr@engnews1.eng.sun.com> <49m4kj$d6v@natasha.rmii.com> NNTP-Posting-Host: taumet.eng.sun.com Content-Type: text X-Newsreader: TIN [version 1.2 PL2] X-Nntp-Posting-Host: mule.gmrc.gecm.com Content-Length: 837 X-Lines: 20 Originator: clamage@taumet