public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Florian Weimer <fw@deneb.enyo.de>
To: "Eddy Ilg" <eddy@fericom.net>
Cc: <gcc-help@gcc.gnu.org>
Subject: Re: Digraphs
Date: Sun, 28 Oct 2001 01:14:00 -0000	[thread overview]
Message-ID: <87r8rogo1c.fsf@deneb.enyo.de> (raw)
In-Reply-To: <002c01c15f37$88ee1970$6300a8c0@Freedom>

"Eddy Ilg" <eddy@fericom.net> writes:

> #define TEST(test) {   \
>    }

> /pub/robocontrol/RoboAPI/module.h:71: parse error before `}'

> There is no spaces behind the \. I have used other compilers and this works
> well. 

Could you provide additional information?  I doubt this is a
preprocessor problem.

> I have found out that cpp recognizes the {} as "digraphs".

No, digraphs are the following tokens:

               <:  :>  <%  %>  %:  %:%:

      reply	other threads:[~2001-10-28  1:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-27 15:34 Digraphs Eddy Ilg
2001-10-28  1:14 ` Florian Weimer [this message]

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=87r8rogo1c.fsf@deneb.enyo.de \
    --to=fw@deneb.enyo.de \
    --cc=eddy@fericom.net \
    --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).