Cast your eyes over the following screenshot
This raises the question
"When exactly is an error expected?"
Surely if you expect an error, it's not actually an error? It's merely the outcome you thought would take place.
Yes, OK, it fits the dictionary definition "a deviation from accuracy or correctness; a mistake, as in action or speech", but that's not the point.
The point is that "error", in its form as a synonym for "mistake" probably isn't the ideal word to apply to the outcome of a computer program when coupled with "unexpected". If you expect it, it's not an error. If it is an error, it's something unexpected.
Redundant tautology is redundant.
But I'm still stymied by the fact that I can't describe the condition in a better way. Unexpected outcome? Doesn't seem right to me. Unknown error? Abnormal exit?
So, my dear blog readers, can you help redefine this most annoying Microsftism?
posted @ Friday, October 8, 2010 3:28 PM