|
in reply to Best practices for module error-reporting
I see 2 kinds of errors: those for the users of the code and those for the developers of the code. For users of the code, just die in a consistent way but you will probably want some kind of framework if you have multiple developers working on the code. If your end product is something to be consumed by the public, then be mindful of your dependencies and try to eliminate them. If your end product installation and maintenance is handled by you, then you usually don't need to worry about NOT using such dependencies.
|
