determining function name in runtime

[shyam]

Hi all

is there any way the determine which function currently is executing in
a process ?

For example we can find the file name using __FILE__
and line number using __LINE__ macros

simillarly is there any macro which gives the function name

thanks shyam

[Vladimir S. Oka]

shyam wrote:

Hi all

is there any way the determine which function currently is executing in
a process ?
I assume you mean program...

For example we can find the file name using __FILE__
and line number using __LINE__ macros

simillarly is there any macro which gives the function name

Yes, and it's __func__ (note double underscores before and after).

--
BR, Vladimir

[Lew Pitcher]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Vladimir S. Oka wrote:

shyam wrote:

Hi all

is there any way the determine which function currently is executing in
a process ?

I assume you mean program...

For example we can find the file name using __FILE__
and line number using __LINE__ macros

simillarly is there any macro which gives the function name

Yes, and it's __func__ (note double underscores before and after).

Note: Unlike __FILE__ and __LINE__, __func__ is not a macro, but a
predefined identifier of local (to the function) scope.

Thus,
char *where_I_am = "I am at line " __LINE__ "\n";
would work, but
char *where_I_am = "I am in function " __func__ "\n";
would not.

OTOH,
printf("I am at line %d in function %s\n",__LINE__, __func__);
will work.
- --

Lew Pitcher, IT Specialist, Corporate Technology Solutions,
Enterprise Technology Solutions, TD Bank Financial Group

(Opinions expressed here are my own, not my employer's)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEBwFDagV FX4UWr64RAlQdAJ 9XT4qQS65GzFFRP O0RDFqxskDA+wCd GWGd
evG1lEWtpMvGxVd vP/Y97RM=
=vy6r
-----END PGP SIGNATURE-----

[MrG{DRGN}]

"Lew Pitcher" <Le*********@td securities.com> wrote in message
news:8j******** ***********@new s20.bellglobal. com...

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Vladimir S. Oka wrote: -snip

, and it's __func__ (note double underscores before and after).
Note: Unlike __FILE__ and __LINE__, __func__ is not a macro, but a
predefined identifier of local (to the function) scope.

Thus,
char *where_I_am = "I am at line " __LINE__ "\n";
would work, but
char *where_I_am = "I am in function " __func__ "\n";
would not.

OTOH,
printf("I am at line %d in function %s\n",__LINE__, __func__);
will work.

Let me guess, __func__ is a C99 feature?
<OT> (which means I can't use it with my compiler msvc 6.0).<OT>

--
MrG{DRGN}

[Vladimir S. Oka]

MrG{DRGN} wrote:

"Lew Pitcher" <Le*********@td securities.com> wrote in message
news:8j******** ***********@new s20.bellglobal. com...

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Vladimir S. Oka wrote:

-snip

, and it's __func__ (note double underscores before and after).

Note: Unlike __FILE__ and __LINE__, __func__ is not a macro, but a
predefined identifier of local (to the function) scope.

Thus,
char *where_I_am = "I am at line " __LINE__ "\n";
would work, but
char *where_I_am = "I am in function " __func__ "\n";
would not.

OTOH,
printf("I am at line %d in function %s\n",__LINE__, __func__);
will work.

Let me guess, __func__ is a C99 feature?
<OT> (which means I can't use it with my compiler msvc 6.0).<OT>

Yes it is.
<OT>I know nothing about M$VC, but it may provide it as an
extension?<OT>

[Ico]

Lew Pitcher <Le*********@td securities.com> wrote:

Note: Unlike __FILE__ and __LINE__, __func__ is not a macro, but a
predefined identifier of local (to the function) scope.

Is there a reason why __func__ is not a macro ?

--
:wq
^X^Cy^K^X^C^C^C ^C

[tmp123]

Ico wrote:

Lew Pitcher <Le*********@td securities.com> wrote:

Note: Unlike __FILE__ and __LINE__, __func__ is not a macro, but a
predefined identifier of local (to the function) scope.

Is there a reason why __func__ is not a macro ?

It is easy for the preprocessor to know the current file and line.
However, it can not known the function name (even it can not known what
is a function) if it doesn't knowns C syntax (and the preprocessor
doesn't).

[Lew Pitcher]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ico wrote:

Lew Pitcher <Le*********@td securities.com> wrote:

Note: Unlike __FILE__ and __LINE__, __func__ is not a macro, but a
predefined identifier of local (to the function) scope.

Is there a reason why __func__ is not a macro ?

My copy of the draft C99 standard doesn't give a reason.

My /guess/ is that __FILE__ and __LINE__ can be implemented as macros
because they do not require any interpretation of the C code (they are
strictly derived from the mechanics of reading the source files).

OTOH, __func__ requires the compiler's interpretation of the code in
order to work, so it cannot be implemented in the same manner as __FILE_
and __LINE__.
- --

Lew Pitcher, IT Specialist, Corporate Technology Solutions,
Enterprise Technology Solutions, TD Bank Financial Group

(Opinions expressed here are my own, not my employer's)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEByGZagV FX4UWr64RAjQJAJ 9unyR7P+JPi14Yw Ci+eKaYF+VeMgCg s0N/
yRzUKfTTmLVMySm RWJUv6us=
=KubY
-----END PGP SIGNATURE-----

[Micah Cowan]

"tmp123" <tm****@menta.n et> writes:

Ico wrote:

Lew Pitcher <Le*********@td securities.com> wrote:

Note: Unlike __FILE__ and __LINE__, __func__ is not a macro, but a
predefined identifier of local (to the function) scope.

Is there a reason why __func__ is not a macro ?

It is easy for the preprocessor to know the current file and line.
However, it can not known the function name (even it can not known what
is a function) if it doesn't knowns C syntax (and the preprocessor
doesn't).

s/doesn't/might not/

Several implementations have provided such a macro. While they /may/
have been handled differently from other macros (I don't actually
know), they were still handled as string literals, and thus you could
make use of the concatenation feature, etc.

But I think the reason you give above is at least why the standard
didn't want to /require/ __func__ to be a macro (and so they required
it to be something else).

-Micah

[Jordan Abel]

On 2006-03-02, MrG{DRGN} <Ia****@here.co m> wrote:

"Lew Pitcher" <Le*********@td securities.com> wrote in message
news:8j******** ***********@new s20.bellglobal. com...

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Vladimir S. Oka wrote:

-snip

, and it's __func__ (note double underscores before and after).

Note: Unlike __FILE__ and __LINE__, __func__ is not a macro, but a
predefined identifier of local (to the function) scope.

Thus,
char *where_I_am = "I am at line " __LINE__ "\n";
would work, but
char *where_I_am = "I am in function " __func__ "\n";
would not.

OTOH,
printf("I am at line %d in function %s\n",__LINE__, __func__);
will work.

Let me guess, __func__ is a C99 feature?
<OT> (which means I can't use it with my compiler msvc 6.0).<OT>

No, but i have a suggestion:

#if __STDC_VERSION_ _ < 199901l
#define WHERE_FMT __FILE__ ":%d"
#define WHERE_ARGS __LINE__
#else
#define WHERE_FMT __FILE__ ":%s:%d"
#define WHERE_ARGS __LINE__,__func __
#endif

fprintf(stderr, "Line printed to stderr at "WHERE_FMT"\n", WHERE_ARGS);

will print file.c:function :42 on c99 systems, file.c:42 on others.