From: "David S. Miller" <davem@redhat.com>
To: R.E.Wolff@BitWizard.nl
Cc: alessandro.suardi@oracle.com, bunk@fs.tum.de,
linux-kernel@vger.kernel.org
Subject: Re: drivers/atm/firestream.c doesn't compile in 2.5.33
Date: Sun, 01 Sep 2002 02:13:08 -0700 (PDT) [thread overview]
Message-ID: <20020901.021308.66278765.davem@redhat.com> (raw)
In-Reply-To: <20020901111433.A23165@bitwizard.nl>
From: Rogier Wolff <R.E.Wolff@BitWizard.nl>
Date: Sun, 1 Sep 2002 11:14:33 +0200
Or did the __FUNCTION__ extension from gcc change? Someone please
explain.....
CPP pasting __FUNCTION__ is now deprecated because for c++ you
cannot do it at compile time. At least that is how I understand
the problem.
The long and short of it is that __FUNCTION__ cpp string pasting
is now illegal.
prev parent reply other threads:[~2002-09-01 9:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-01 0:30 drivers/atm/firestream.c doesn't compile in 2.5.33 Adrian Bunk
2002-09-01 1:28 ` Alessandro Suardi
2002-09-01 9:14 ` Rogier Wolff
2002-09-01 9:13 ` David S. Miller [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=20020901.021308.66278765.davem@redhat.com \
--to=davem@redhat.com \
--cc=R.E.Wolff@BitWizard.nl \
--cc=alessandro.suardi@oracle.com \
--cc=bunk@fs.tum.de \
--cc=linux-kernel@vger.kernel.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 NNTP newsgroup(s).