This is something that I’ve known for a while, but always seem to forget when it comes to actually implementing it in my code.

When catching an exception, most people catch it as a variable, such as “ex” and then just do a “throw ex” and throw that exception back up the chain. This is probably not what you want. When the stack trace/error information comes back from that exception, it will show as having occurred where your “throw ex” was. This isn’t really helpful if your “try” block contains a lot of code.

Instead, you should just simply write “throw”, without passing a specific exception. This allows the stack trace to show the original location of the error (instead of where you caught the exception and threw it again.) This information is much more helpful when debugging..

And now you know too!

I love this rendition; something very pure and calming about it.

http://www.atasteforthetheatrical.com/

It looks amazing. I saw it on the big screen tonight in front of I Am Legend, and I can’t wait to see the film next year.

Let’s put a smile on that face!

These are supposed international one-sheets. First one comes from Collider, the second comes from AlloCine. First heard about (appropriately enough) via FirstShowing. At first I thought it was fake (because just the Batman one was posted, and it just seemed strange.) But now I get the concept, after seeing the other “Joker” poster. Pretty darn cool, and whoever’s responsible for them did a great job.

_{(or download an mp3.)}

This is the best ever. Just kick off your shoes, curl up next to the fire with a cup of apple cider, and enjoy.

(As heard on the Mikey Show on Rock 105.3)