Forrest is exactly right. I would add to it, it's not just about it ending
up in the right place, but about it getting caught at all, though in this
context they're pretty much the same thing.
Ya, sorry, it really wasn't necessarily the best example, but often
presenting reasons for why an API is failing, in order to convince someone
that it is actually a bug, you must first convince them it's a legitimate
use case. The result is a pretty strained example (though in real code, it
comes up regularly), but I was just trying to provide an example of when
someone might generate a new error in a callback after the originating
function returned an error.
On Wed, Nov 14, 2012 at 7:32 PM, Forrest L Norvell <forr...@newrelic.com>wrote:
Better a little with righteousness
than much gain with injustice.