| Subject: | Croak on failure of requiring an external pacakge |
Brian, I would just assume that Brick->_load_external_packages croaked
instead of carping when an attempt to require an external package fails.
Just carping can make tracking down a bug that leads to failure of a
given external package unnecessarily difficult. I would assume that if I
asked for functionality from a given package and it failed, it would be
a showstopper.
If nothing else, could you create a simple backstop method called
something like handle_failure_on_require that would allow us to alter
that behavior?