VC好象只支持宏__FILE__，__LINE__，但不支持__FUNCTION__，不知有没有好的替代方法？

[rtdb]

RT

[flyelf]

vc没有这个宏，关注ing

[newsb]

vc确实没有，可能微软觉得file 和line就能唯一确定位置了，所以没有加入func的宏

[DentistryDoctor]

使用VC7.0/7.1呀。

[snaill]

Microsoft-Specific Predefined Macros

__FUNCTION__
Valid only within a function and returns the undecorated name of the enclosing function (as a string). __FUNCTION__ is not expanded if you use the /EP or /P compiler option.

[holyeagle]

可能是函数的通用性不强吧，如果是全局的的变量，就没有函数，不能相应定位了。而且，函数在最初的词法上不好分析，因为这时候只是分析语法，还没到函数分析，遇到语法错误就可以停止，不用再分析函数，如果这时候去定位函数会多作无用的工作。

[jruv]

snaill() ,强！

[oyljerry]

__FILE__
This macro expands to the name of the current input file, in the form of a C string constant. This is the path by which the preprocessor opened the file, not the short name specified in #include or as the input file name argument. For example, "/usr/local/include/myheader.h" is a possible expansion of this macro.

__LINE__
This macro expands to the current input line number, in the form of a decimal integer constant. While we call it a predefined macro, it's a pretty strange macro, since its "definition" changes with each new line of source code.
__FILE__ and __LINE__ are useful in generating an error message to report an inconsistency detected by the program; the message can state the source line at which the inconsistency was detected. For example,

fprintf (stderr, "Internal error: "
"negative string length "
"%d at %s, line %d.",
length, __FILE__, __LINE__);

An #include directive changes the expansions of __FILE__ and __LINE__ to correspond to the included file. At the end of that file, when processing resumes on the input file that contained the #include directive, the expansions of __FILE__ and __LINE__ revert to the values they had before the #include (but __LINE__ is then incremented by one as processing moves to the line after the #include).

A #line directive changes __LINE__, and may change __FILE__ as well. See Line Control.

C99 introduces __func__, and GCC has provided __FUNCTION__ for a long time. Both of these are strings containing the name of the current function (there are slight semantic differences; see the GCC manual). Neither of them is a macro; the preprocessor does not know the name of the current function. They tend to be useful in conjunction with __FILE__ and __LINE__, though.