C# version of __FUNCTION__ macro

后端 未结 6 1773
有刺的猬
有刺的猬 2021-02-19 01:18

Does anyone has a good solution for a C# version of the C++ __FUNCTION__ macro? The compiler does not seem to like it.

相关标签:
6条回答
  • 2021-02-19 01:35

    Unfortunately there is no equivalent version of that macro in C#. I don't consider the GetCurrentMethodName() solution equivalent to the C++ __FUNCTION__ macro. Namely becase the C++ version is a compile time computation of the name. For C# this is a runtime calculation and incurs a performance hit.

    I'm not making any assumtions about the severity of the cost but there is one

    0 讨论(0)
  • 2021-02-19 01:35

    The following should work, although it will be evaluated at runtime instead of during compilation.

    System.Reflection.MethodBase.GetCurrentMethod().Name
    
    0 讨论(0)
  • 2021-02-19 01:37

    Try using this instead.

    System.Reflection.MethodBase.GetCurrentMethod().Name
    

    C# doesn't have __LINE__ or __FUNCTION__ macros like C++ but there are equivalents

    0 讨论(0)
  • 2021-02-19 01:43

    I use this:

    public static string CallerName([CallerMemberName] string callerName = "")
    {
        return callerName;
    }
    

    Usage example:

    s_log.DebugFormat("{0}", CallerName());
    

    The down side of using it is that every time you want to print the caller name, you need to jump to the function ==> time consuming & performance hit! So, I use it for debugging perpose and if I need to print also in production code, I usually inline the function name into the log.Debug, e.g. :

    s_log.Debug("CallerName");
    

    HTH..

    0 讨论(0)
  • 2021-02-19 01:44

    What I currently use is a function like this:

    using System.Diagnostics;
    
    public string __Function() {
        StackTrace stackTrace = new StackTrace();
        return stackTrace.GetFrame(1).GetMethod().Name;
    }
    

    When I need __FUNCTION__, I just call the __Function() instead. For example:

    Debug.Assert(false, __Function() + ": Unhandled option");
    

    Of course this solution uses reflection too, but it is the best option I can find. Since I only use it for Debugging (not Tracing in release builds) the performance hit is not important.

    I guess what I should do is create debug functions and tag them with

    [ Conditional("Debug") ]
    

    instead, but I haven't got around to that.

    Thanks to Jeff Mastry for his solution to this.

    0 讨论(0)
  • 2021-02-19 01:58

    This is added in .NET 4.5.

    See @roken's answer here:

    Do __LINE__ __FILE__ equivalents exist in C#?

    0 讨论(0)
提交回复
热议问题