Re: Try .. Catch with no Exception needed.
- From: Lasse Vågsæther Karlsen <lasse@xxxxxxxxxxx>
- Date: Fri, 25 Jan 2008 11:21:40 +0100
Nicholas Paldino [.NET/C# MVP] wrote:
It should be noted that if you catch an Exception (or just have a catch statement) that your application won't necessarily be "stable". In catching all exceptions (instead of just ones you know are going to be thrown) you are corrupting your application state to some degree, and if you aren't fastidious about defining the boundaries of your application, you will have unexpected errors because of exceptions that were thrown and ignored in other areas.
In other words, be very careful about proceeding in this manner. There are reasons that exceptions are thrown, and you should ignore them at your own peril.
For some reason an image of an old map popped into my head containing "Here there be dragons!" :)
--
Lasse Vågsæther Karlsen
mailto:lasse@xxxxxxxxxxx
http://presentationmode.blogspot.com/
PGP KeyID: 0xBCDEA2E3
.
- References:
- Try .. Catch with no Exception needed.
- From: RP
- Re: Try .. Catch with no Exception needed.
- From: Nicholas Paldino [.NET/C# MVP]
- Try .. Catch with no Exception needed.
- Prev by Date: Re: Composite Keys with <TKey,TValue> pairs generic collections
- Next by Date: Re: DirectoryServices.AccountManagement
- Previous by thread: Re: Try .. Catch with no Exception needed.
- Next by thread: DataTable question
- Index(es):
Relevant Pages
|