public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: mskhan@hss.hns.com
To: gcc-help@gcc.gnu.org
Cc: mskhan@hss.hns.com
Subject: pasting "." and "something" does not give a valid preprocessing token..
Date: Thu, 24 Apr 2003 06:29:00 -0000	[thread overview]
Message-ID: <OF592EF5A1.78F3D25F-ON65256D12.00233D38@hss.hns.com> (raw)






I've just installed gcc 3.2 and I get the warning from the subject line when
compiling code that worked just fine with 2.95.3. Can anyone tell me what the
 warning means and how it can be rectified.

The offending code is a macro :

#define EMUL_TRACE(level, format, args...)     proc::theTrace->logTrace((level,  ##format , ##args)


where "Proc" is a class defined as

class Proc
{

. ..........

static TraceLog * theTrace;

}

and TraceLog  is another class defined as

class TraceLog
{
.............
public:
............
void logTrace(int severity, char* stringToBeLogged, ...)
.............

}

Thanks in advance....
Sanjay



"DISCLAIMER: This message is proprietary to Hughes Software Systems Limited
(HSS) and is intended solely for the use of the individual to whom it is
addressed. It may contain  privileged or confidential information and
should not be circulated or used for any purpose other than for what it is
intended. If you have received this message in error, please notify the
originator immediately. If you are not the intended recipient, you are
notified that you are strictly prohibited from using, copying, altering, or
disclosing the contents of this message. HSS accepts no responsibility for
loss or damage arising from the use of the information transmitted by this
email including damage from virus."

             reply	other threads:[~2003-04-24  6:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-24  6:29 mskhan [this message]
2003-04-24  6:41 ` LLeweLLyn Reese
  -- strict thread matches above, loose matches on Subject: below --
2003-08-19  8:19 Marc Eberhard
2003-08-19  8:35 ` Nathan Sidwell
2003-08-19  9:12   ` Marc Eberhard
2003-04-24  7:46 mskhan
2003-03-10  8:59 Mihnea Balta
2003-03-10  9:02 ` Mihnea Balta
2003-03-10  9:05   ` Florian Weimer
2003-03-10  9:04 ` Momchil Velikov
2003-03-10  9:08   ` Mihnea Balta

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=OF592EF5A1.78F3D25F-ON65256D12.00233D38@hss.hns.com \
    --to=mskhan@hss.hns.com \
    --cc=gcc-help@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: link
Be 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).