[Mono-bugs] [Bug 24103] Changed - finally blocks running at incorrect time

[bugzilla-daemon@rocky.ximian.com]

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 ben.hutchison@intamission.com.

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

--- shadow/24103	Wed May  1 23:27:54 2002
+++ shadow/24103.tmp.25955	Fri May 10 05:59:53 2002
@@ -1,14 +1,14 @@
 Bug#: 24103
 Product: Mono/Runtime
 Version: unspecified
-OS: 
+OS: unknown
 OS Details: 
 Status: NEW   
 Resolution: 
-Severity: 
+Severity: Unknown
 Priority: Critical
 Component: misc
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: linus@linus.com               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
@@ -75,6 +75,17 @@
 blocks run.
 
 I'm not sure why they chose to do this, but it does look intentional. My
 only guess so far is that they wanted to allow developers the
 opportunity to inspect the program's state with a debugger before any of
 the finally blocks ran.
+
+------- Additional Comments From ben.hutchison@intamission.com  2002-05-10 05:59 -------
+The .Net behavior seems dubious when compared against the description 
+of exception propagation in C# language def section 8.10. The mono 
+behavior seems closer to the spec, which is that finally staements 
+are run immediately after the try, and before progagating the 
+exception.
+
+.Net seems to be eagerly inferring that the exception will not be 
+handled, and saying an unhandled  exception has been received before 
+actually progagating it. Not correct, IMHO.