[Mono-bugs] [Bug 78252][Min] New - [PATCH] make CS3014 warning (CLSCompliant(true) in non-CLSCompliant assembly)

[bugzilla-daemon at 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 atsushi at ximian.com.

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

--- shadow/78252	2006-05-01 00:40:15.000000000 -0400
+++ shadow/78252.tmp.12724	2006-05-01 00:40:15.000000000 -0400
@@ -0,0 +1,47 @@
+Bug#: 78252
+Product: Mono: Compilers
+Version: 1.1
+OS: 
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Minor
+Component: C#
+AssignedTo: rharinath at novell.com                            
+ReportedBy: atsushi at ximian.com               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: [PATCH] make CS3014 warning (CLSCompliant(true) in non-CLSCompliant assembly)
+
+In .NET 1.0 csc CLSCompliant(true) inside non-CLSCompliant assembly
+(CS3014) causes an error. In .NET 2.0 it became a warning.
+
+using System;
+
+[CLSCompliant (true)]
+public class Test
+{
+}
+
+I quickly searched CLSCompliant check related sections in ECMA-334 but I
+could not find any, so am guessing it is MS extension.
+
+A fix:
+
+Index: decl.cs
+===================================================================
+--- decl.cs	(revision 60029)
++++ decl.cs	(working copy)
+@@ -477,7 +477,7 @@
+ 
+ 			if (!CodeGen.Assembly.IsClsCompliant) {
+ 				if (HasClsCompliantAttribute) {
+-					Report.Error (3014, Location,
++					Report.Warning (3014, 1, Location,
+ 						"`{0}' cannot be marked as CLS-compliant because the assembly is not
+marked as CLS-compliant",
+ 						GetSignatureForError ());
+ 				}