This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Request for more info out of __FUNCTION__
- To: gcc <gcc at gcc dot gnu dot org>
- Subject: Re: Request for more info out of __FUNCTION__
- From: Benjamin Scherrey <scherrey at switchco dot com>
- Date: Wed, 02 Feb 2000 15:06:45 -0600
- CC: David Edelsohn <dje at watson dot ibm dot com>, meissner at cygnus dot com
- Organization: Proteus Technologies, Inc.
- References: <200002021918.OAA22572@mal-ach.watson.ibm.com>
- Reply-To: scherrey at proteus-tech dot com
Thanx to Dave & Michael for the quick responses. I either missed it,
or have old docs when I first wrote my DEBUG macro. However, this is a
bit of a case of "Be careful what you wish for..." as I'm getting a
lot more info than I wanted and my debug trace listing is way too wide
now. The NameSpace::Class::MethodName is fine (I could even do without
the namespace) but all the parameter information (especially with
templates) is just too much. I guess I'll have to run it through some
script to strip out the extra stuff.
thanx again & later,
Ben Scherrey
David Edelsohn wrote:
> Have you looked at the __PRETTY_FUNCTION__ macro provided by GCC?
> See "Function Names as Strings" under "C Extensions" in the GCC
> documentation.