[Mono-devel-list] casting method to delegates compiles

[Patrick Beard]

On Jun 24, 2004, at 1:25 PM, Todd Berman wrote:

> Matthias Kempka wrote:
>> Duncan Mak wrote:
>>> By default, we enable 2.0 features in mcs (those that are 
>>> implemented).
>> Well, I'm not into your design process, but up to now I can't come to 
>> like this. As stupid C# programming user I somehow expect code that 
>> compiles at one compiler to compile with every C# compiler, that is 
>> because my teacher told me C# compilers only can call itself so if 
>> they compile *exactly* the language that was specified in the ECMA.
>
> This feature is in the ECMA, your MS.NET compiler is too old to 
> compile it properly, if you were to use the compiler from the whidbey 
> beta stuff it would compile fine.
>
> Duncan explained exactly how to write the code so that a C# 1.0 
> compiler will compile it perfectly fine.
>
>> While using mcs I would be way happier knowing that I now am 
>> programming C# version x.y and that any other compiler that compiles 
>> C# version x.y will compile my program. (isn't that the idea of 
>> standardisation?)
>> The way I see it now is dialects coming up.
>
> This has nothing to do with dialects, and everything to do with 
> evolving standards. The standard is changing, we change with it, c'est 
> la vie.

Is there a strict 1.0 only compatibility mode? This would help a lot to 
check for unintentional usage of 2.0 features.

- Patrick