D
dbeavon
Guest
I just wanted to point out that most programmers who use structured error handling in other languages know that there is an overhead cost associated with throwing and catching exceptions. The inclusion of the stack frames is just part of that cost and should be done by default. Without the stack frames we sometimes have to search through hundreds or thousands of lines of buried code within all code paths leading out of the do/catch. It's like searching for a needle in the haystack - even if you *do* know the error message. After many months of using SEH in OE, I'm getting pretty discouraged by that exercise ; but whenever I read about the errorstack parameter, the documentation is written in a way that will frighten people away from it in production, or else they might try to only use it temporarily. If it can't be used by default then Progress has more work to do. It is not fair or reasonable to force ABL programmers to make large performance compromises, or create their own custom mechanisms for capturing stack frames. Furthermore i should probably say that I always try to *avoid* features that aren't enabled by default in OE because I'd rather not stray away from the herd, for fear of obscure bugs.
Continue reading...
Continue reading...