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 [EMAIL PROTECTED]

http://bugzilla.ximian.com/show_bug.cgi?id=78422

--- shadow/78422        2006-05-17 06:32:29.000000000 -0400
+++ shadow/78422.tmp.16462      2006-05-17 06:48:33.000000000 -0400
@@ -1,13 +1,13 @@
 Bug#: 78422
 Product: Mono: Compilers
 Version: unspecified
 OS: unknown
 OS Details: 
-Status: NEW   
-Resolution: 
+Status: RESOLVED   
+Resolution: NOTABUG
 Severity: Unknown
 Priority: Wishlist
 Component: C#
 AssignedTo: [EMAIL PROTECTED]                            
 ReportedBy: [EMAIL PROTECTED]               
 QAContact: [EMAIL PROTECTED]
@@ -71,6 +71,15 @@
 while we treat it as
 
   ( (int) ( *(int*)((int)p) ) ) = 0
 
 If you really want to keep your code, with the redundant (int) cast, I
 welcome you to fix mcs ;-)
+
+------- Additional Comments From [EMAIL PROTECTED]  2006-05-17 06:48 -------
+On further thought, I can't think of any straightforward way for a
+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.
_______________________________________________
mono-bugs maillist  -  [email protected]
http://lists.ximian.com/mailman/listinfo/mono-bugs

Reply via email to