If clients don't subscribe to events

[Guest]

I have a class which exposes number of events. If client doesn't subscibe to
an event, I get a runtime error when event is raised. What's the way to deal
with it?, other than making sure all events are subscribed to.

 

[Mythran]

I have a class which exposes number of events. If client doesn't subscibe
to
an event, I get a runtime error when event is raised. What's the way to
deal
with it?, other than making sure all events are subscribed to.

if (this.EventHandler != null) {
// raise event
}

hth

Mythran

 

[Guest]

Thanks!
It's one of those "Duhhh!!!" moments.

if (this.EventHandler != null) {
// raise event
}

hth

Mythran

 

[Jon Skeet [C# MVP]]

Thanks!
It's one of those "Duhhh!!!" moments.

Actually, it's not quite that simple - because that pattern isn't
threadsafe. EventHandler's "nullity" could change between the test and
you trying to raise the event.

See http://www.pobox.com/~skeet/csharp/threads/lockchoice.shtml for my
suggested pattern.

 

[Mythran]

Actually, it's not quite that simple - because that pattern isn't
threadsafe. EventHandler's "nullity" could change between the test and
you trying to raise the event.

See http://www.pobox.com/~skeet/csharp/threads/lockchoice.shtml for my
suggested pattern.

Hmm, really? That is Microsoft's recommended approach, but I do see how it
would not be thread safe w/o some sort of lock...

Mythran

 

[Jon Skeet [C# MVP]]

Hmm, really? That is Microsoft's recommended approach, but I do see how it
would not be thread safe w/o some sort of lock...

Microsoft unfortunately often forgets thread-safety when it puts
together code patterns...

(Of course, it's not a problem in the situation where you don't need
your type to be thread-safe. Most types probably *shouldn't* be thread-
safe, IME.)

 

[Guest]

Actually I am dealing with multithreaded application. But it's really 2
threads, UI and worker thread, only 1 thread at a time will own that code
section ,so I don't think thread-safety is something to worry about. Or
should I?