[Mono-bugs] [Bug 78252][Min] Changed - [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 marek.safar at seznam.cz.

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

--- shadow/78252	2006-05-01 00:40:15.000000000 -0400
+++ shadow/78252.tmp.5535	2006-05-02 12:28:00.000000000 -0400
@@ -1,17 +1,17 @@
 Bug#: 78252
 Product: Mono: Compilers
 Version: 1.1
-OS: 
+OS: unknown
 OS Details: 
 Status: NEW   
 Resolution: 
-Severity: 
+Severity: Unknown
 Priority: Minor
 Component: C#
-AssignedTo: rharinath at novell.com                            
+AssignedTo: marek.safar at seznam.cz                            
 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)
@@ -42,6 +42,17 @@
 -					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 ());
  				}
+
+------- Additional Comments From marek.safar at seznam.cz  2006-05-02 12:28 -------
+Well, I am not a fan of this MS change. I would prefer to keep the CLS
+errors to be still errors. The reason is simple when I mark assembly
+CLS Compliant I expect that it will be which we cannot guranted when
+CLS violations are report as the warnings.
+I really don't understand why MS changed this.
+
+I know that Miguel already turned one of the errors to warning but I
+would like to keep the code consistent.
+