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=81563 --- shadow/81563 2007-05-15 18:08:37.000000000 -0400 +++ shadow/81563.tmp.4614 2007-05-16 14:07:46.000000000 -0400 @@ -1,13 +1,13 @@ Bug#: 81563 Product: Mono: Compilers Version: 1.2 OS: unknown OS Details: -Status: RESOLVED -Resolution: NOTABUG +Status: REOPENED +Resolution: Severity: Unknown Priority: Wishlist Component: C# AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] QAContact: [EMAIL PROTECTED] @@ -65,6 +65,15 @@ Looks like it was REMOVED in .Net 2.0. So it should now be allowed. ------- Additional Comments From [EMAIL PROTECTED] 2007-05-15 18:08 ------- This is not a bug. The behavior changed between 1.1 and 2.0 which means that mcs reports this error and gmcs not. + +------- Additional Comments From [EMAIL PROTECTED] 2007-05-16 14:07 ------- +Not sure what version of mcs Wasabi was using, but mcs from SVN no +longer reports CS1533 when calling Invoke on a delegate. + +Shouldn't mcs be compatible with csc 1.x in this case ? + +For gmcs it's of course ok to no longer report CS1533 since that +matches the behaviour of csc 2.x, so no changes necessary there. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
