G'day cavac,

While I don't necessarily disagree with anything you wrote there, I'm wondering if we're talking at cross-purposes.

In the past, I've certainly written modules which, as part of loading, attempt to include some other module whose name is determined dynamically (perhaps based on environment, config, or similar). I would expect failure to be handled a little more elegantly:

Some/Module.pm failed to load because ...
[download]

Rather than what you refer to as "crash-and-burn":

Some/Module.pm did not return a true value ...
[download]

Could you provide some skeleton code that clarifies the scenario you're describing? Thankyou.