Bug 15814 - Initialize events with empty delegates
Summary: Initialize events with empty delegates
Status: NEW
Alias: None
Product: Tools
Classification: Mono
Component: Gendarme ()
Version: unspecified
Hardware: All All
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2013-10-30 08:09 UTC by Andres G. Aragoneses
Modified: 2013-10-30 08:09 UTC (History)
1 user (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report for Bug 15814 on GitHub or Developer Community if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: GitHub Markdown or Developer Community HTML
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:
Status:
NEW

Description Andres G. Aragoneses 2013-10-30 08:09:23 UTC
The rule http://www.mono-project.com/Gendarme.Rules.Concurrency#ProtectCallToEventDelegatesRule gives a great suggestion for avoiding race conditions.

But there should be another rule which recommends this practice:

http://stackoverflow.com/questions/9033/hidden-features-of-c/9282#9282

This would problably be only a "style" rule, which just makes the safe approach that ProtectCallToEventDelegatesRule proposes, a bit less verbose.

Or maybe we should modify ProtectCallToEventDelegatesRule to just suggest this simpler approach?