Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

C# version of __FUNCTION__ macro

Tags:

c#

.net

macros

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

like image 360
Filip Frącz Avatar asked Nov 03 '08 18:11

Filip Frącz


People also ask

What C is used for?

C programming language is a machine-independent programming language that is mainly used to create many types of applications and operating systems such as Windows, and other complicated programs such as the Oracle database, Git, Python interpreter, and games and is considered a programming foundation in the process of ...

What is the full name of C?

In the real sense it has no meaning or full form. It was developed by Dennis Ritchie and Ken Thompson at AT&T bell Lab. First, they used to call it as B language then later they made some improvement into it and renamed it as C and its superscript as C++ which was invented by Dr. Stroustroupe.

Is C language easy?

C is a general-purpose language that most programmers learn before moving on to more complex languages. From Unix and Windows to Tic Tac Toe and Photoshop, several of the most commonly used applications today have been built on C. It is easy to learn because: A simple syntax with only 32 keywords.

How old is the letter C?

The letter c was applied by French orthographists in the 12th century to represent the sound ts in English, and this sound developed into the simpler sibilant s.


2 Answers

Try using this instead.

System.Reflection.MethodBase.GetCurrentMethod().Name

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

like image 155
Eoin Campbell Avatar answered Sep 30 '22 20:09

Eoin Campbell


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.

like image 27
Mark Booth Avatar answered Sep 30 '22 20:09

Mark Booth