I'm looking to add some type of error indicators to my modules. Basically, I want to be able to attempt to perform an operation, detect it easily from the calling location, and then handle it in some graceful and appropriate way. IE:
$myObjInstance->myFunction or confess "problems were found".$myObjInstance->errstr;
At first I thought about using the standard constants that are used by perl built in functions, like open and eval, for holding the error reason. Ie $!, $@, etc:
This just felt wrong, although it is technically allowed by perl internals. Eventually I remembered that DBI, makes use of "err" for error code, "errstr" for error message, "state" for random state information, and a couple other less used values.
My question is this. Do any of you know of any standards for holding error states returned to the user of a module. DBI is the only module that I could find that doesn't just choose to "Carp" their way out of problems. While this works for a lot of things, it's not nearly as clean in my opinion to have to wrap such code in an eval in order to catch error conditions. What are y'alls thoughts on the matter?
I apologize if this is not the proper venue for this type of question, but I would appreciate any thoughts or experience that you would have to share on the matter. Even if it would simply to point to other CPAN modules that handle error conditions in a die-less way.
Thanks
$myObjInstance->myFunction or confess "problems were found".$myObjInstance->errstr;
At first I thought about using the standard constants that are used by perl built in functions, like open and eval, for holding the error reason. Ie $!, $@, etc:
This just felt wrong, although it is technically allowed by perl internals. Eventually I remembered that DBI, makes use of "err" for error code, "errstr" for error message, "state" for random state information, and a couple other less used values.
My question is this. Do any of you know of any standards for holding error states returned to the user of a module. DBI is the only module that I could find that doesn't just choose to "Carp" their way out of problems. While this works for a lot of things, it's not nearly as clean in my opinion to have to wrap such code in an eval in order to catch error conditions. What are y'alls thoughts on the matter?
I apologize if this is not the proper venue for this type of question, but I would appreciate any thoughts or experience that you would have to share on the matter. Even if it would simply to point to other CPAN modules that handle error conditions in a die-less way.
Thanks