public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Martin Ambuhl <mambuhl@earthlink.net>
To: help-gcc@gnu.org
Subject: Re: how to declare dynamic 2-dimensional array in C++?
Date: Mon, 03 Jan 2000 10:16:00 -0000	[thread overview]
Message-ID: <3870E536.5A00FA79@earthlink.net> (raw)
In-Reply-To: <84pus001rnr@enews2.newsguy.com>

"Johnny Favorite (it means \"Writhing Tentacle of Death\")" wrote:
> 
> Alex Vinokur wrote:
> > 3. __PRETTY_FUNCTION__
> >     --FUNCTION__
> 
> Since your other two examples were pretty cool-sounding I have to ask about
> this one.  What the heck does __PRETTY_FUNCTION__ do?

File: gcc.info,  Node: Function Names,  Next: Return Address,  Prev:
Incomplete Enums,  Up: C Extensions

Function Names as Strings
=========================

   GNU CC predefines two string variables to be the name of the current
function.  The variable `__FUNCTION__' is the name of the function as
it appears in the source.  The variable `__PRETTY_FUNCTION__' is the
name of the function pretty printed in a language specific fashion.

   These names are always the same in a C function, but in a C++
function they may be different.  For example, this program:

     extern "C" {
     extern int printf (char *, ...);
     }
     
     class a {
      public:
       sub (int i)
         {
           printf ("__FUNCTION__ = %s\n", __FUNCTION__);
           printf ("__PRETTY_FUNCTION__ = %s\n", __PRETTY_FUNCTION__);
         }
     };
     
     int
     main (void)
     {
       a ax;
       ax.sub (0);
       return 0;
     }

gives this output:

     __FUNCTION__ = sub
     __PRETTY_FUNCTION__ = int  a::sub (int)

   These names are not macros: they are predefined string variables.
For example, `#ifdef __FUNCTION__' does not have any special meaning
inside a function, since the preprocessor does not do anything special
with the identifier `__FUNCTION__'.



-- 
Martin Ambuhl	mambuhl@earthlink.net

What one knows is, in youth, of little moment; they know enough who
know how to learn. - Henry Adams

A thick skin is a gift from God. - Konrad Adenauer
__________________________________________________________
Fight spam now!
Get your free anti-spam service: http://www.brightmail.com

WARNING: multiple messages have this Message-ID
From: Martin Ambuhl <mambuhl@earthlink.net>
To: help-gcc@gnu.org
Subject: Re: how to declare dynamic 2-dimensional array in C++?
Date: Sat, 01 Apr 2000 00:00:00 -0000	[thread overview]
Message-ID: <3870E536.5A00FA79@earthlink.net> (raw)
Message-ID: <20000401000000.-KkCu_Wl8mUb41eLQaKje45-4x3xTnjB2CXOqwh9bOs@z> (raw)
In-Reply-To: <84pus001rnr@enews2.newsguy.com>

"Johnny Favorite (it means \"Writhing Tentacle of Death\")" wrote:
> 
> Alex Vinokur wrote:
> > 3. __PRETTY_FUNCTION__
> >     --FUNCTION__
> 
> Since your other two examples were pretty cool-sounding I have to ask about
> this one.  What the heck does __PRETTY_FUNCTION__ do?

File: gcc.info,  Node: Function Names,  Next: Return Address,  Prev:
Incomplete Enums,  Up: C Extensions

Function Names as Strings
=========================

   GNU CC predefines two string variables to be the name of the current
function.  The variable `__FUNCTION__' is the name of the function as
it appears in the source.  The variable `__PRETTY_FUNCTION__' is the
name of the function pretty printed in a language specific fashion.

   These names are always the same in a C function, but in a C++
function they may be different.  For example, this program:

     extern "C" {
     extern int printf (char *, ...);
     }
     
     class a {
      public:
       sub (int i)
         {
           printf ("__FUNCTION__ = %s\n", __FUNCTION__);
           printf ("__PRETTY_FUNCTION__ = %s\n", __PRETTY_FUNCTION__);
         }
     };
     
     int
     main (void)
     {
       a ax;
       ax.sub (0);
       return 0;
     }

gives this output:

     __FUNCTION__ = sub
     __PRETTY_FUNCTION__ = int  a::sub (int)

   These names are not macros: they are predefined string variables.
For example, `#ifdef __FUNCTION__' does not have any special meaning
inside a function, since the preprocessor does not do anything special
with the identifier `__FUNCTION__'.



-- 
Martin Ambuhl	mambuhl@earthlink.net

What one knows is, in youth, of little moment; they know enough who
know how to learn. - Henry Adams

A thick skin is a gift from God. - Konrad Adenauer
__________________________________________________________
Fight spam now!
Get your free anti-spam service: http://www.brightmail.com

  reply	other threads:[~2000-01-03 10:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <386da233.0@news.tm.net.my>
     [not found] ` <84n59m$daj$1@nnrp1.deja.com>
     [not found]   ` <386fac89@eeyore.callnetuk.com>
2000-01-02 21:35     ` Alex Vinokur
2000-01-03  3:55       ` Johnny Favorite (it means "Writhing Tentacle of Death")
2000-01-03 10:16         ` Martin Ambuhl [this message]
2000-01-03 11:04           ` Greg Comeau
2000-04-01  0:00             ` Greg Comeau
2000-01-04  4:24           ` Johnny Favorite (it means "Writhing Tentacle of Death")
2000-04-01  0:00             ` Johnny Favorite (it means "Writhing Tentacle of Death")
2000-04-01  0:00           ` Martin Ambuhl
2000-01-04  5:55         ` __PRETTY_FUNCTION__, functions and templates Alex Vinokur
2000-04-01  0:00           ` Alex Vinokur
2000-04-01  0:00         ` how to declare dynamic 2-dimensional array in C++? Johnny Favorite (it means "Writhing Tentacle of Death")
2000-04-01  0:00       ` Alex Vinokur

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=3870E536.5A00FA79@earthlink.net \
    --to=mambuhl@earthlink.net \
    --cc=help-gcc@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).