
Signature
Jon Skeet - <skeet@pobox.com>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
World class .NET training in the UK: http://iterativetraining.co.uk
>> I understand but the solution for how .NET framework has solved it when
>> dealing with const between assemblies was not the best choice.
>
> Well, it's useful occasionally - and easy to avoid, just by using
> static readonly instead.
Not to split hairs or anything, but if it is constant, why is it
changing? :)

Signature
Lasse Vågsæther Karlsen
mailto:lasse@vkarlsen.no
http://presentationmode.blogspot.com/
PGP KeyID: 0xBCDEA2E3
Jon Skeet [C# MVP] - 20 Feb 2008 14:00 GMT
> > Well, it's useful occasionally - and easy to avoid, just by using
> > static readonly instead.
>
> Not to split hairs or anything, but if it is constant, why is it
> changing? :)
Because someone *thought* it was a constant with one value, but that
turned out to be wrong. Or because someone used "const" without really
thinking about whether or not it was genuinely a constant.
I'm not saying it should happen, just that it does and it's worth being
aware of the consequences :)

Signature
Jon Skeet - <skeet@pobox.com>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
World class .NET training in the UK: http://iterativetraining.co.uk