Bug 16084 - Inconsistency with MS.NET for events in interfaces.
Summary: Inconsistency with MS.NET for events in interfaces.
Status: RESOLVED NORESPONSE
Alias: None
Product: Compilers
Classification: Mono
Component: C# ()
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Marek Safar
URL:
Depends on:
Blocks:
 
Reported: 2013-11-09 18:11 UTC by Marius Ungureanu
Modified: 2014-01-31 06:20 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 on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED NORESPONSE

Description Marius Ungureanu 2013-11-09 18:11:22 UTC
using System;

namespace Mcs_Sample
{
	interface myInt
	{
		event Action a;
	}

	class myIntImpl : myInt
	{
		public event Action a;
		event Action myInt.a { add {} remove {} }
	}

	class MainClass
	{
		public static void Main (string[] args)
		{
		}
	}
}


This is a test case for something that builds on MS.NET and Mono pre-3.2.5. With 3.2.5, this is broken.

As seen in NRefactory.Tests, TypeSystemTests.TestCase.cs : 397
Comment 1 Marek Safar 2013-11-10 12:23:42 UTC
I cannot reproduce it with master, what is the full error message?
Comment 2 Marek Safar 2014-01-31 06:09:32 UTC
No response
Comment 3 Marius Ungureanu 2014-01-31 06:20:18 UTC
It has been fixed since then. It was my pupil having an outdated mono.