recentpopularlog in

mcherm : exceptions   14

An essay showing that it is harder to use exceptions safely than most people think.
programming  via:HackerNews  exceptions 
august 2015 by mcherm
C++: do you (really) write exception safe code? - Stack Overflow
A really well-written essay on how to think about writing exception safe code in C++. Convinces me that it's very nice to have stronger support for exceptions in languages like Java and C#, but this is a good way to work with C++.
programming  exceptions  C++ 
april 2013 by mcherm
Checked Exceptions Might Have Their Place, But It Isn't In Java
Another person making the case why Java's checked exceptions are broken. This time with good examples.
languagedesign  progamming  java  exceptions  via:JamesIry  JamesIry 
february 2012 by mcherm
On Removing Java Checked Exceptions By Means of Perversion: One Div Zero
This is a very clever Java hack. It's a way to throw checked exceptions without the compiler checking them. Yeah.
hack  exceptions  java  JamesIry  via:JamesIry  programming 
august 2010 by mcherm
The best way to handle exceptions: David R. MacIver
Don't catch an exception then log something meaningless and exit. You lose the stack trace.
exceptions  programming  DavidMacIver 
april 2010 by mcherm
Exception as the primary error handling mechanism? - comp.lang.python | Google Groups
An excellent explanation of why it's better (often) to use exceptions rather than returning and testing for an error value. Focused on Python, but applicable generally.
programming  exceptions  python 
january 2010 by mcherm
Fabulous Adventures In Coding : Locks and exceptions do not mix
An excellent explanation of some gory details of handling locks and exceptions. Illustrates a time when deadlock might be what you WANT!
programming  threading  concurrency  exceptions  via:EricLippert  EricLippert 
march 2009 by mcherm
8 ways to report errors in Haskell
There are LOTS of different ways to handle exceptions (errors) in Haskell -- none is standardized. And the result is a horrible mishmash. Lesson: when building any language, build in exceptions from the start -- they're a really nice model.
haskell  languagedesign  programming  exceptions 
october 2008 by mcherm
Fabulous Adventures In Coding : Vexing exceptions
Eric Lippert's opinion on when you should catch exceptions: There are 4 types. "Fatal" (the system is busted) -- don't bother catching these, you can't fix it. "Boneheaded" (bug in your code) -- don't catch these, it hides the error. "Vexing" (library throws exception when it shouldn't) -- catch for now; write libraries better. And "Exogenous" (required because of real-life problems) -- catch these.
programming  exceptions  EricLippert  codingstyle 
september 2008 by mcherm
Avoiding Checked Exceptions - O'Reilly ONJava Blog
I didn't realize that you could throw checked exceptions from a class that doesn't declare them if you use Unsafe.getUnsafe() (a Sun internal class).
java  exceptions  hacking 
january 2008 by mcherm
JohnsonChapter4.pdf (application/pdf Object)
Very nice chapter from a Java programming book. May be worth buying the book itself! Among other things, it has an excellent writeup of MY beliefs on use of checked exceptions.
exceptions  java  programming  articles/programming  books  onlinebooks 
october 2007 by mcherm
Effective Java Exceptions
When to use checked vs unchecked exceptions in Java. Good ideas!
programming  java  exceptions 
january 2007 by mcherm

Copy this bookmark:

to read