How can you "handle" the exception if you don't know what type it is? What happens if the next version of the CLR adds another exception type that is thrown by that function; how can you possibly deal with that exception properly?
It's always easier to write less robust code; but, that doesn't mean we should. http://www.peterRitchie.com/ On Mon, 19 Sep 2005 09:05:28 -0400, Eames, Andrew <[EMAIL PROTECTED]> wrote: >There is some argument for a few exceptions (:)) - for instance >File.Open throws a variety of exceptions, not all of which derive from >IOException - its much easier to just catch System.Exception in this >case > Andrew > =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
