|
Re: distinguishing between failures and errors: msg#00137java.junit.user
--- In junit@xxxx, Mike Clark <mike@xxxx> wrote: > neil_swingler wrote: > >Apart from making refactoring harder, checked exceptions also > >make exception handling code more error prone. These are things > >I have seen frequently where developers write code to handle checked > >exceptions: > > > >o Do nothing > >o Print/log message (but not the stacktrace) > >o Wrap the exception but lose the cause exception and it's stacktrace > >o catch Exception (also catches all those RuntimeExceptions they > > had forgotten about > > > > How does using unchecked exceptions help those developers? > If they don't have to write any exception handling code they can't code errors into it. The exceptions can propogate to a single point to be logged.
|
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: OT: Bad examples everywhere (Was: distinguishing between failures and errors), Eric Heikkila |
|---|---|
| Next by Date: | Re: OT: Bad examples everywhere (Was: distinguishing between failures and errors), Jason Rogers |
| Previous by Thread: | Re: Re: distinguishing between failures and errors, Mike Clark |
| Next by Thread: | Re: Re: distinguishing between failures and errors, Mike Clark |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |