From -4594324169289678893 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f78e5,83aac58a7c7d6c46 X-Google-Attributes: gidf78e5,public From: James Kuyper Subject: Re: Advice: C9X's __func__ on C++ Date: 1999/06/10 Message-ID: <375FBADC.A43579C3@wizard.net>#1/1 X-Deja-AN: 487963477 Content-Transfer-Encoding: 7bit Approved: Valentin Bonnard References: X-Original-Date: Thu, 10 Jun 1999 09:17:16 -0400 Content-Type: text/plain; charset=us-ascii Organization: Not Enough X-Auth: PGPMoose V1.1 PGP comp.std.c++ iQBVAwUAN1/j6awEuYhIxRhxAQGurgH9GfKTfwhcVkhCEo0qAIBT0mIYkgkBtl2m qmhx0DlOGLOysVVhAGhdQ0R3t5w0E0E/QxpTPgRoWl/SR+6+MzAiuw== =3npO Mime-Version: 1.0 Newsgroups: comp.std.c++ Ken Hagan wrote: > > If __func__ is a preprocessor symbol, then I can imagine using > the decorated name for some purposes. That would give us 3 to > choose from -- the immediate name, the fully qualified name, and > the mangled name. No - it's a local static const char[]. I think that's why it's lower case, rather than upper case like (most of?) the other preprocessor symbols defined by the C standard. --- [ comp.std.c++ is moderated. To submit articles, try just posting with ] [ your news-reader. If that fails, use mailto:std-c++@ncar.ucar.edu ] [ --- Please see the FAQ before posting. --- ] [ FAQ: http://reality.sgi.com/austern_mti/std-c++/faq.html ]