Article View: comp.std.c++
Article #750Re: Help Preprocessor
From: Jerry Schwarz
Date: Mon, 05 Oct 1992 16:13
Date: Mon, 05 Oct 1992 16:13
29 lines
1468 bytes
1468 bytes
My apologies for the empty article that I just inadvertantly
distributed with this title.
In article <1992Oct4.085733.7703@ucc.su.OZ.AU>, maxtal@extro.ucc.su.OZ.AU (John MAX Skaller) writes:
|> I've got a few minor problems with the specifications for the
|> preprocessor.
|>
|> The issue of incomplete /* comments in preprocessor commands is one.
|>
|> #define fred a + /* incomplete
|> comment spans lines here */ b
|>
|> Is the above legal?
|>
I belive it is very likely that the final C++ standard will
adapt the the ANSI/ISO C standard's preprocessing mechanism.
(The main difference is the existence of // comments). Under
that assumption the above will certainly be legal. Treatment
of "#include <...>" will also be essentially identical to
that in the C standard.
But at the moment many C++ implementations are built on
non standard preprocessors and their handling of these
issues may not be identical to that of a standard conforming
C compiler. For maximum portability, don't put comments
into #defines
-- Jerry Schwarz
Technical Details
Message-ID:
<1992Oct5.161316.7711@lucid.com>Path:
arc1-ca.pugleaf.net!sparky!uunet!stanford.edu!lucid.com!lucid.com!jssReferences:
<1992Oct4.085733.7703@ucc.su.OZ.AU>Show Full Headers
Complete Article Headers
Newsgroups: comp.std.c++ Path: arc1-ca.pugleaf.net!sparky!uunet!stanford.edu!lucid.com!lucid.com!jss From: jss@lucid.com (Jerry Schwarz) Subject: Re: Help Preprocessor Message-ID: <1992Oct5.161316.7711@lucid.com> Sender: usenet@lucid.com Reply-To: jss@lucid.com (Jerry Schwarz) Organization: Lucid, Inc. References: <1992Oct4.085733.7703@ucc.su.OZ.AU> Date: Mon, 5 Oct 92 16:13:16 GMT Lines: 30