|
You're right, that was an oversight. Thank you for pointing it out.
In fact, any time general exceptions are caught and thrown again using a known exception alias from CLIF::Exceptions (which, as you noticed, is a technique used internally by CLIF to partition a potentially unlimited set of exception types into known classes so a context-specific diagnostic message can be printed on the console), the code should use the throw_XXX_exception( error => $e ) syntax to preserve the exception object.
This will be fixed in the next version. |
