I've seen a couple different ways of calling events in libraries.
1. Check to see if sub exists with subExists then if so raiseEvent.
2. Just call raiseEvent.
Now, since I haven't seen a problem either way I'm assuming the first thing raiseEvent does is to call subExists? So, depending on your school of though as to whether cleaner code or less overhead for method calls are better we should be fine just calling raiseEvent right?
I ask because I'm making a view with only one event and to make proper use of the view you have to use the event. Since the event should always exist then calling subExists only to have raiseEvent call it a 2nd time would be overkill.
1. Check to see if sub exists with subExists then if so raiseEvent.
2. Just call raiseEvent.
Now, since I haven't seen a problem either way I'm assuming the first thing raiseEvent does is to call subExists? So, depending on your school of though as to whether cleaner code or less overhead for method calls are better we should be fine just calling raiseEvent right?
I ask because I'm making a view with only one event and to make proper use of the view you have to use the event. Since the event should always exist then calling subExists only to have raiseEvent call it a 2nd time would be overkill.