public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Neil Booth <neil@daikokuya.co.uk> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/8297: problem with preprocessor Date: Mon, 21 Oct 2002 12:56:00 -0000 [thread overview] Message-ID: <20021021195601.6869.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/8297; it has been noted by GNATS. From: Neil Booth <neil@daikokuya.co.uk> To: Ritesh Goel <riteshg@pune.tcs.co.in> Cc: zack@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: c++/8297: problem with preprocessor Date: Mon, 21 Oct 2002 20:53:58 +0100 Ritesh Goel wrote:- > Thanx for ur immediate response . > I want to give comments in my program with using keyword "COMMENT" not > with // . that should be eliminated during preprocessing . > > as COMMENT Line in comment > instead of > // Line in comment > > I tried to make it using #define but it insert space between that with > version gcc3.0 . > It is doing that with previous versions . But there also in the preprocessed > output it is replacing that with // . > So when i am taking preprocessed output there, it is taking it as comment . > And all the comments should be removed in preprocessing . but it is not > doing that . > > > I am not getting anyway to to do that . Can u help me in that . This is a Microsoft-ism that we will not duplicate. There is no way to do what you want with standard C or C++. Neil.
next reply other threads:[~2002-10-21 19:56 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-10-21 12:56 Neil Booth [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-10-21 0:16 Ritesh Goel 2002-10-20 23:46 Zack Weinberg 2002-10-20 23:44 zack 2002-10-20 22:56 riteshg
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20021021195601.6869.qmail@sources.redhat.com \ --to=neil@daikokuya.co.uk \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).