From: Ross Combs <rocombs@cs.nmsu.edu>
To: martin@loewis.home.cs.tu-berlin.de, rocombs@cs.nmsu.edu
Cc: gcc@gcc.gnu.org
Subject: Re: Compiler Directive to List Defined Macros?
Date: Thu, 29 Jun 2000 15:49:00 -0000 [thread overview]
Message-ID: <200006292249.QAA30985@quito.cs.nmsu.edu> (raw)
> > So __PRETTY_FUNCTION__ has existed for a long time in gcc? I can trust
> > that even old copies will support this?
>
> Yes. I could check when it was first introduced - but so could you.
> Then you could define a reliable test based on the values of __GNUC__
> and __GNUC_MINOR__
Look like 2.7 introduced this feature from looking at the release notes.
In 2.8 __FUNCTION__ and __PRETTY_FUNCTION__ became functions instead of
strings. I'll add in the tst like this:
#if defined(__GNUC__) && \
(__GNUC__ == 2 && __GNUC_MINOR__ >= 7) || \
__GNUC__ > 2)
> (*) It still is, and some people claim that __func__ should have been
> one of these, also, to allow concatenation as in
>
> __FILE__ ":" __FUNCTION__
Hmm. That is how I originally tried to use it. It is also annoying that
I couldn't find a way to stringize __LINE__ and then concatenate it to
__FILE__. But such things can be worked around.
-Ross
next reply other threads:[~2000-06-29 15:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-29 15:49 Ross Combs [this message]
2000-06-30 1:36 ` Neil Booth
-- strict thread matches above, loose matches on Subject: below --
2000-06-30 14:34 Ross Combs
2000-06-29 8:28 Ross Combs
2000-06-29 13:44 ` Martin v. Loewis
2000-06-29 8:18 Ross Combs
2000-06-29 11:38 ` Geoff Keating
2000-06-28 17:19 Ross Combs
2000-06-28 19:40 ` Geoff Keating
2000-06-29 0:39 ` Martin v. Loewis
2000-06-28 6:44 Bolan Meek
2000-06-28 7:27 ` Franz Sirl
2000-06-28 7:35 ` Bolan Meek
2000-06-28 7:56 ` Alexandre Oliva
2000-06-28 8:06 ` Bolan Meek
2000-06-28 8:14 ` Alexandre Oliva
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=200006292249.QAA30985@quito.cs.nmsu.edu \
--to=rocombs@cs.nmsu.edu \
--cc=gcc@gcc.gnu.org \
--cc=martin@loewis.home.cs.tu-berlin.de \
/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).