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=81685 --- shadow/81685 2007-05-23 19:10:04.000000000 -0400 +++ shadow/81685.tmp.23716 2007-05-24 04:47:15.000000000 -0400 @@ -143,6 +143,16 @@ I have not looked at what Silverlight does (someone mentioned during the conversation that they just stop execution of the managed code and return an error). Under these conditions it does not seem worth to implement, I thought that Silvelright might be able to throw and have the exception be caught. + +------- Additional Comments From [EMAIL PROTECTED] 2007-05-24 04:47 ------- +Jim Miller's remarks might be correct for the default CLR host, +but a sophisticated MS CRL host is definitely informed about critical +errors, including stack overflows. The host can even choose a priori +which action the CLR should perform when a specific error condition +has occurred. Although some errors (stack overflows) are not really +recoverable, the host can choose to remain alive (MSSQL is such a +host). + _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
