G
GSchug
Guest
1. Is it a good thing that a CATCH for Progress.Lang.Error (etc.) can catch STOP conditions associated with error messages? Is this what you would expect, or would you rather have to code explicitly to catch any STOP condition? Don't want to code STOP explicitly. Don't care for difference between old ERROR and STOP. Both are the same to me (at a first glance). Of course in special cases, I'd like to differentiate, but in 99% of the cases, there's no difference for me. 2. Do you see an issue in that STOP can possibly get caught before it would have before, which is either never caught or at a DO ON STOP higher up the call stack? no 3. Is there anything else that OpenEdge Engineering should consider? no. I'd need that feature very soon. We've tried to introduce structured error handling in the application and still have this ugly "do on stop" statements. Buuuh.
Continue reading...
Continue reading...