in reply to Best practices for module error-reporting

It is probably a matter of personal opinion or taste, but I would avoid (if possible) adding dependencies that are not really necessary for the core features of your new module. They may dissuade people from using your module.

This of course does not apply to core modules. I would also recommend Carp, which makes it possible to throw exception (and/or issue warnings) useful from the standpoint of the user, including stack trace and so on..

  • Comment on Re: Best practices for module error-reporting