From -1269266797435337409 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f78e5,f0f9f7db2408f2ce X-Google-Attributes: gidf78e5,public X-Google-ArrivalTime: 1993-04-23 13:36:50 PST Path: gmd.de!ira.uka.de!howland.reston.ans.net!zaphod.mps.ohio-state.edu!cs.utexas.edu!uunet!pilchuck!fnx!nazgul!bright From: bright@nazgul.UUCP (Walter Bright) Newsgroups: comp.std.c++ Subject: Re: ANSI Releases of C++ Compilers Message-ID: <1708@nazgul.UUCP> Date: 23 Apr 93 07:40:35 GMT References: Reply-To: bright@nazgul.UUCP (Walter Bright) Distribution: na Organization: Zortech, Seattle Lines: 17 In article rotherme@bcstec.ca.boeing.com (Pete Rothermel) writes: /I'm wondering what the compiler vendors are going to do /after the final release of the ANSI C++ standard. Will /they make a new release that is "ANSI compliant"? How about /a compiler switch that flags the now ANSI portions of code as /warnings. Let's hear from you vendors. What are you planning? We'll probably do the same thing we do for C. We provide a -A (ANSI compile) switch, which is primarilly useful for running ANSI test suites. The default mode will reflect the way the language is actually used by the majority of our customers. Our customers pay the bills, not the ANSI committee, so we set up the compiler the way they want it. (An example of this are trigraphs, which I have yet to see in a program that is not some sort of test suite. Processing trigraphs significantly slows compilation, so by default they are not done. Another example are // comments in C.)