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=77353 --- shadow/77353 2006-01-27 18:40:41.000000000 -0500 +++ shadow/77353.tmp.23987 2006-01-30 02:02:00.000000000 -0500 @@ -5,18 +5,18 @@ OS Details: Status: NEW Resolution: Severity: Unknown Priority: Minor Component: C# -AssignedTo: [EMAIL PROTECTED] +AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] QAContact: [EMAIL PROTECTED] TargetMilestone: --- URL: -Summary: Compiler Error for valid code using `ref` on a delegate +Summary: delegate generation might have to cope with local conflicts. Please fill in this template when reporting a bug, unless you know what you are doing. Description of Problem: Using `ref' on a paramater within a delegate declaration results in a @@ -56,6 +56,21 @@ ------- Additional Comments From [EMAIL PROTECTED] 2006-01-25 11:45 ------- As I'm investigating the possibility to port an enterprise ERP system to run with Mono, this bug is fairly severe for me. ------- Additional Comments From [EMAIL PROTECTED] 2006-01-27 18:38 ------- As a workaround, use a different name for "result", rename it to "_result" + +------- Additional Comments From [EMAIL PROTECTED] 2006-01-30 02:01 ------- +Explanation: the problem is that the declaration of a delegate creates +three methods: Invoke, BeginInvoke and EndInvoke, and those have +standard names. + +The problem in this bug is that the name of the parameters in his +delegates conflicts with these names. + +The solution is not straight forward. The MS compiler sometimes +renames the parameters, and sometimes produces methods with two +parameters names with the same name which might indicate a partial +workaround in their compiler. + + _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
