There's nothing cargo-cultish about catching and redirecting errors. The technique is independent of any one particular error.

I see your point, but I suppose it depends on the level of analysis and the type of error. "cargo cult programming", as I understand it, is when a programmer repeatedly uses a chunk of code or a technique without ever really understanding why they are doing so.

So on one level "catching errors" might suffice as an explanation for a programmer doing what you suggest; on a deeper level, however, that explanation might not be satisfactory if the programmer has no idea where the errors originate or why. (my broad definition would even include tried and true techniques such as using stict without ever understanding the utility or purpose of its usage.)

Anyway -- my first comment was not meant so much as critcism as it was a colorful way to express my curiousity -- when you stated that it "caught something odd once" I was interested in hearing more information about the rare beast in question.

Matt

P.S. If my notion of "cargo cult" is incorrect, then please feel free to ignore my cargo cultish use of the phrase "cargo cult." ;)