[Mono-list] Const weirdness, revisited...

Tom tom@abwaerts.be
Fri, 18 Feb 2005 18:50:45 +0100

Content-Type: text/plain;
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hey ho,

=46irst post to the list, so I'm hoping I won't make too much of a fool=20
out of myself.

Every once in a while, I suddenly think that yes, I too can be a=20
programmer. In that spirit, I've piled up a nice bunch of beginner=20
books, the most recent of them being "Learning C#". The fact that I=20
tend to be unable to do something useful with the basic knowledge I=20
gathered is totally irrelevant here. Maybe I should start buying=20
intermediate books, for a start.

My question being, however: when I initialize a const int to a certain=20
int value, and later on reassign it, Mono merrily tells me that=20
compilation succeeded. Like so:

const int meh =3D 5;
meh =3D 10;

Kind of unexpected... :-/ The only post mentioning something at least=20
quite similar, is that of Jonathan Stowe in April 2002 [1]. Apart from=20
that, I can't seem to find anything related to Mono not being capable=20
of pointing me to the most basic of mistakes.

Could someone give me a clue? Or is it supposed to be that way? I didn't=20
find any bugs either, but that might be just me...


[1] lists.ximian.com/archives/public/mono-list/2002-April/004801.html

key: http://tmp.verbreyt.be/files/abwaerts.asc

Content-Type: application/pgp-signature

Version: GnuPG v1.4.0 (GNU/Linux)