L
Laura Stern
Guest
Ah. I see your point! But here is the reality. I just did some timings where an error was generated resulting in a 10-level deep stack. Constructing the call stack takes roughly .01 to .05 milliseconds for each error, depending on the machine. Windows seems to be fastest relative to solaris and Linux! In addition, we do not generate the call stack if you are using NO-ERROR. So we are talking about taking this extra time only when there is an unexpected error and you are using a CATCH block. That does not seem at all onerous to me and certainly does NOT warrant that statement in the documentation. So no, we are not taking a different approach to structured error handling from other languages. We are just sensitive about performance and took the cautions approach, for better or worse. So again, this statement in the doc is way too strong and we will amend it. Therefore, as I originally said, you should just turn on -errorstack and not worry about it.
Continue reading...
Continue reading...