sactoheath's Journal: Throwing Exceptions

From our internal blogs website today:
Application Error
An error occurred while processing your request
Details

Exception of type System.OutOfMemoryException was thrown.

Ok, I have to say this reminds me of college, working on some Apple Mac II's, and getting "An error of type -2 has occurred."

I was always baffled at the Apple error messages. Even Microsoft's cryptic errors are more explanatory than this. I mean...how many times have you gotten the blue screen with an error like IRQ_NOT_LESS_THAN_OR_EQUAL? At least you have some text there that gives you an indication of where the problem is. But "Type -2".....how do you have negative numbered errors in the first place?

But really that's not why I decided this was funny. What made me laugh was the whole "was thrown." That feels like corporate jargon to me.

"Oh yeah I was working on the new widget today but it totally threw an error and I was like, oh my gah!"

How exactly do you "throw" an exception. How far does it get thrown? Does someone catch the exception and make it exceptional? Do they throw it back? Should there be a followup message that says "Exceptional of type System.HasPlentyOfExceptionalMemoryNow was caught"?

Do I have too much free time on my hands?