[Mono-bugs] [Bug 78422][Wis] Changed - [REGRESSION] Parsing unsafe
pointer value assignment
bugzilla-daemon at bugzilla.ximian.com
bugzilla-daemon at bugzilla.ximian.com
Wed May 17 10:23:13 EDT 2006
Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.
Changed by grompf at sublimeintervention.com.
http://bugzilla.ximian.com/show_bug.cgi?id=78422
--- shadow/78422 2006-05-17 06:48:33.000000000 -0400
+++ shadow/78422.tmp.24423 2006-05-17 10:23:13.000000000 -0400
@@ -80,6 +80,22 @@
disambiguation rule to parse the code other than how mcs does. The
compiler has to _know_ that it's a cast as soon as it sees (int), and
it doesn't need any further lookahead. Casts bind tighter than
assignment.
So, I'm changing this to NOTABUG.
+
+------- Additional Comments From grompf at sublimeintervention.com 2006-05-17 10:23 -------
+hari,
+
+ I have changed the code that exposed this (in fact the "erroneous" cast was there because
+of a old mcs bug that required it a long time ago) but I personally disagree with NOTABUG.
+I know we dont bug track microsoft in every instance; but in the COMPILER? We should be
+compiling the same code they do (in my opinion).
+
+ Its a process desicion rather than a technical one; I just want to wave the flag that if they
+compile it; I think we probably should as well.
+
+ Admittedly this is a edge case.
+
+-g
+
More information about the mono-bugs
mailing list