testing event == nullptr

Hot Topic

I got this error when compiling "Error c2784"
converting float to string and string to float
VC8, Adding __event to non-CLR code gives error C2712
Couple .NET 2k5/CLR enabled DLL questions
Using a C++ dll exported functions in C prog...
What is the licensing policy CRT library shipped with VC++?
DLL in mfc
Tracking Reference (%), value, ref??
reference counting problem
VC8, Adding __event to non-CLR code gives error C2712

Visual C++

Can it build win32 dll which calls c# .net assembly ?
Recommended Books
unhandled exception during the process of deleting an exception
Can't build WMI/C++ example in Visual Studio
Opening Files
Classes and Declarations
Structure member definition not recognized
reference to an int array
Reference dll
Other people testing my app

testing event == nullptr


With the old syntax you had to test whether there was any handler connected to an event by writing
  if (myevent != nullptr) myevent(this, myargs);

With the new syntax you no longer have to perform the test, which is good, but what if I really want to know if there are handlers What would be the syntax then

Chris.

Answer this question

testing event == nullptr

  • Chien-hao Wen

    Hi Chris: the feeling of the C++/CLI design team was that an event is an abstraction of add, remove and raise and that users shouldn't really be peeking behind the curtain Smile. If you really want this level of control then I would suggest that you use a raw delegate instead of an event.

  • testing event == nullptr
Answer this question