Here's a pattern I've used many timess successfully in the past:
Since this runs whenever the module is loaded it will complain at startup if one of the implementations is incorrect.
For another layer of abstraction you can combine the above with use of Class::Factory as the parent class and associating each of the implementations with a simple name rather than a class name.
Chris
M-x auto-bs-mode
In reply to Re: Is dynamic loading of pm's a bad thing?
by lachoy
in thread Is dynamic loading of pm's a bad thing?
by CassJ
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |