From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/5.3] No __FUNCTION__
Date: Sun, 29 Sep 2002 09:54:00 -0000 [thread overview]
Message-ID: <3D973047.6030609@redhat.com> (raw)
In-Reply-To: <20020929164614.GA32746@nevyn.them.org>
> On Sun, Sep 29, 2002 at 11:41:00AM -0400, Andrew Cagney wrote:
>
>> I've committed the attached (with a hesatant ok from MarkK) (HEAD and
>> branch).
>>
>> What GDB needs is something that works regardless of the compiler.
>>
>> Andrew
>
>
> Where is this usage of __FUNCTION__ not portable? Concatenating it
> with things, now there's a problem; but I don't remember any compiler
> that couldn't handle function(__FUNCTION__).
The macro __FUNCTION__ isn't part of ISO C 90.
Andrew
prev parent reply other threads:[~2002-09-29 16:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-29 8:41 Andrew Cagney
2002-09-29 9:45 ` Daniel Jacobowitz
2002-09-29 9:54 ` Andrew Cagney [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=3D973047.6030609@redhat.com \
--to=ac131313@redhat.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
/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