Timeline for Encapsulating common Try-Catch code. Is this a known pattern? Is it good or bad?
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 9, 2019 at 18:33 | history | edited | dfhwze |
tag
|
|
| Jul 9, 2019 at 18:32 | answer | added | dfhwze | timeline score: 1 | |
| Dec 14, 2013 at 23:46 | comment | added | BrainSlugs83 | I like this pattern; this is pretty slick. | |
| May 25, 2012 at 14:34 | answer | added | Heretic Monkey | timeline score: 2 | |
| May 24, 2012 at 14:26 | answer | added | Stefan Hanke | timeline score: 2 | |
| May 24, 2012 at 11:45 | history | edited | Rudi | CC BY-SA 3.0 |
updated the title
|
| May 24, 2012 at 11:44 | comment | added | Rudi |
@Laurent I am essentially extending the logger class (the ILog interface here is from the [netcommon.sourceforge.net/](Common.Logging) framework). Yet please focus on the use of the TryCatchxxx method; encapsulating common TryCatch logic.
|
|
| May 23, 2012 at 17:15 | history | tweeted | twitter.com/#!/StackCodeReview/status/205346223060819968 | ||
| May 23, 2012 at 14:22 | comment | added | laurent | I don't know about this kind of pattern, but wouldn't it be more proper to extend the logger class and silence the exceptions you don't need? | |
| May 23, 2012 at 13:50 | history | asked | Rudi | CC BY-SA 3.0 |