C#: Nonzero-based arrays are not CLS-compliant

Question

I am currently reading Albahari's C# 3.0 in a Nutshell and on pg. 241, whilst talking about Array indexing, he says this:

Nonzero-based arrays are not CLS (Common Language Specification)-compliant

What does it mean exactly, for nonzero arrays to not be CLS compliant ? And what implications does it have on your code?

[Update]

Here is a link to the page of the book.

Answer 1

The CLS (Common Language Specification) lays the groundwork for a common set of rules for compliance that guarantees that other languages (VB.NET, F#, etc.) can use assemblies that you have built with C#. A nonzero-based array would not be compliant as other languages expect arrays to be zero-based.

Here is an example that is easier to understand:

class Foo
{
    public void Bar() { }
    public void bar() { } 
}

This type would not be CLS compliant since it contains two members that differ in name only by type. How would someone using VB.NET disambiguate between Bar and bar since the VB.NET compiler is not case-sensitive?

So basically the CLS is a bunch of rules like this to guarantee interoperability between languages.

Answer 2

CLS compliance is mostly about making sure that your code is as broadly compatible with other languages as possible. It includes things like not exposing public members which differ only by case (which would confuse VB, which is case-insensitive). See this MSDN article for more information, along with the common language specification itself.

Answer 3

I addition to what's been said, nonzero-based arrays exist solely to ease transition for existing VB6 code (mainly by the automatic migration tool) since in VB6, array indexing could start from an arbitrary number, not necessarily zero.

Due to the CLS compliance issue (and other considerations), it's not recommended to ever use them in .NET (even when programming VB.NET). Furthermore, their use is rather restricted. It's easier just to do an offset translation by encapsulating the array inside a class and writing an appropriate index access operator.