Search results for "module:autodie::exception"

autodie::exception - Exceptions from autodying functions. River stage four • 456 direct dependents • 2215 total dependents

When an autodie enabled function fails, it generates an "autodie::exception" object. This can be interrogated to determine further information about the error that occurred. This document is broken into two sections; those methods that are most usefu...

TODDR/autodie-2.34 - 22 Jan 2021 17:05:24 UTC

autodie::exception::system - Exceptions from autodying system(). River stage four • 456 direct dependents • 2215 total dependents

This is a autodie::exception class for failures from the "system" command. Presently there is no way to interrogate an "autodie::exception::system" object for the command, exit status, and other information you'd expect such an object to hold. The in...

TODDR/autodie-2.34 - 22 Jan 2021 17:05:24 UTC

autodie - Replace functions with ones that succeed or die with lexical scope River stage four • 456 direct dependents • 2215 total dependents

bIlujDI' yIchegh()Qo'; yIHegh()! It is better to die() than to return() in failure. -- Klingon programming proverb. The "autodie" pragma provides a convenient way to replace functions that normally return false on failure with equivalents that throw ...

TODDR/autodie-2.34 - 22 Jan 2021 17:05:24 UTC

autodie::skip - Skip a package when throwing autodie exceptions River stage four • 456 direct dependents • 2215 total dependents

This dummy class exists to signal that the class inheriting it should be skipped when reporting exceptions from autodie. This is useful for utility classes like Path::Tiny that wish to report the location of where they were called on failure. If your...

TODDR/autodie-2.34 - 22 Jan 2021 17:05:24 UTC
4 results (0.026 seconds)