Personally, i see a design problem here ... but i don't know exactly what you are building, either. ;)
Generally speaking, i think that a module should have an interface that is not dependent on something like Getopt::Long. I feel that Option modules are better fitted with CLI (command line interface) scripts. What if you wanted to used the module from a CGI script or mod_perl -- AKA, a Web interface? If so, then your module should not be pulling arguments from STDIN, instead the client should read from STDIN (or the socket) and simply pass the data as method arguments to the module. It's not really that much more work, but the flexibility outweighs the extra typing, IMHO.
UPDATE:
Sounds valid and interesting. Please let me know how it goes. :)
jeffa
L-LL-L--L-LL-L--L-LL-L-- -R--R-RR-R--R-RR-R--R-RR B--B--B--B--B--B--B--B-- H---H---H---H---H---H--- (the triplet paradiddle with high-hat)
In reply to Re: Multiple GetOptions?
by jeffa
in thread Multiple GetOptions?
by PetaMem
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |