[Mono-bugs] [Bug 58055][Blo] Changed - volatile interface members dont' work

[bugzilla-daemon@bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by iain@mccoy.id.au.

http://bugzilla.ximian.com/show_bug.cgi?id=58055

--- shadow/58055	2004-05-07 05:14:11.000000000 -0400
+++ shadow/58055.tmp.26408	2004-05-07 05:22:39.000000000 -0400
@@ -2,13 +2,13 @@
 Product: Mono: Compilers
 Version: unspecified
 OS: All
 OS Details: 
 Status: NEW   
 Resolution: 
-Severity: 
+Severity: Unknown
 Priority: Blocker
 Component: C#
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: michi@zeroc.com               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
@@ -33,6 +33,22 @@
 interface type.
 
 ------- Additional Comments From iain@mccoy.id.au  2004-05-07 05:14 -------
 Created an attachment (id=7629)
 does this look good?
 
+
+------- Additional Comments From iain@mccoy.id.au  2004-05-07 05:22 -------
+The relevant sections of the spec are
+http://msdn.microsoft.com/library/default.asp?url=/library/en-us/csspec/html/vclrfcsharpspec_10_4_3.asp
+(or 17.4.3 in monodoc) and
+http://msdn.microsoft.com/library/default.asp?url=/library/en-us/csspec/html/vclrfcsharpspec_A_2.asp
+(or 25.2 in monodoc).
+
+The patch I'm attaching changes the set of things for which this error
+message is emitted, so that it lets non-value-type types through - I
+can't see a way to directly check for reference-type-ness.
+
+This does fix the reported bug, but I don't know if the runtime copes
+properly with volatile reference types - this patch probably ought not
+be applied unless somebody knowledgable enough to do so decides that
+it's probably safe from the runtime's perspective.