Forum Post: Structured error handling and debugging

[Stefan Drissen]

I am using ROUTINE-LEVEL ON ERROR UNDO, THROW with one CATCH in the main block of an AppServer entry procedure. This seems to render the debugger useless, since any error is picked up by the CATCH in the main block, resulting in all context of any internal procedure which caused the error being lost since it is out of scope. This seems to be where -undothrow 1 could become useful - ie remove the routine-level on error statement and use -undothrow 1 in testing / production and leave it out in development?

Continue reading...