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=80980

--- shadow/80980        2007-03-30 08:58:55.000000000 -0500
+++ shadow/80980.tmp.13828      2007-03-30 15:50:30.000000000 -0500
@@ -1,12 +1,12 @@
 Bug#: 80980
 Product: Mono: Class Libraries
 Version: 1.2
 OS: GNU/Linux [Other]
 OS Details: 
-Status: REOPENED   
+Status: ASSIGNED   
 Resolution: 
 Severity: Unknown
 Priority: Normal
 Component: libgdiplus
 AssignedTo: [EMAIL PROTECTED]                            
 ReportedBy: [EMAIL PROTECTED]               
@@ -210,6 +210,15 @@
 OutOfMemoryException is more likely.
 
 I'll try a few (and you can too ;-) and change the exception to what
 seems to be the most common one.
 
 
+
+------- Additional Comments From [EMAIL PROTECTED]  2007-03-30 15:50 -------
+I got test case resulting in both ExternalException and
+OutOfMemoryException. Both derives from SystemException so "correct
+code" should deal (catch) on this level (or it can fail anyway). So
+throwing an Exception (like we do currently) isn't correct.
+
+Now selecting which exception is easy as CheckStatus already deal with
+OoM (and not EE).
_______________________________________________
mono-bugs maillist  -  [email protected]
http://lists.ximian.com/mailman/listinfo/mono-bugs

Reply via email to