---- Reported by ginga@kit.hi-ho.ne.jp 2003-10-25 03:03:18 MST ----

If target classes violates rules on CLS compliance, MS.NET csc reports 
them, but mcs seems not. At least I noticed that there are same named 
members in case-insensitive, it is not reported by mcs. For example,

--------------
using System;

[assembly:CLSCompliant (true)]
public class Test
{
        public Test Foo;
        protected Test foo;
}
--------------

This class cannot be compiled under csc.

$ csc /t:library clscompliant.cs
Microsoft (R) Visual C# .NET Compiler version 7.10.3052.4
for Microsoft (R) .NET Framework version 1.1.4322
Copyright (C) Microsoft Corporation 2001-2002. All rights reserved.

clscompliant.cs(7,17): error CS3005: Identifier 'Test.foo' differing only 
in case is not CLS-compliant
clscompliant.cs(6,14): (Location of symbol related to previous error)


How often does this happen? 
- always.



---- Additional Comments From bmaurer@users.sf.net 2003-11-18 12:54:20 MST ----



*** This bug has been marked as a duplicate of https://bugzilla.novell.com/show_bug.cgi?id=MONO30285 ***


Unknown operating system unknown. Setting to default OS "Other".
This bug was marked DUPLICATE in the database it was moved from.
    Changing resolution to "MOVED"