I am not totally new to perl and modules. Mostly I've been a user of modules and I am writing some modules and planning to upload to CPAN. I have some experience writing simple perl module (.pm) files and using them straightaway in my own application. Now I'm learning to use tools like h2xs, module-maker to develop proper (standard) way of doing things. I have read module tutorials on 'perlmonks'. So the question is how do I structure my module if I would like to separate interface and implementations?
Let's say I've Foo::Bar and client will only use Foo::Bar. but Foo::Bar is just interface and there may be multiple concrete implementations. (maybe something like DBI, IOHandle?) So Foo::Bar::Implementation1 and Foo::Bar::Implementation2 maybe developed by different developers. Does that mean one developer will be writing his/her own h2xs Foo::Bar::Implementation ?
In reply to perl module structure by pwagyi
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |