Looking at your code, I see that requiring the function names to have no sigil (rather than making it optional) simplifies the code.
It saved me a couple of lines, and a lot of logic, indeed. Since I'm against using sigils on subs, I decided to simply not support them. (Note that of course, when you are referencing a sub, using a sigil is more or less needed (you don't want to type *subname{CODE} all the time :P)). I don't care much about how many lines my code has. But as logic is added, maintainability decreases.
Keeping that note, why have non-functions supported, when by far the most common thing to export is functions.
I quite like for example how LWP::Simple can export $ua. It makes life pleasant. And I can implement it using a few regexes and a hash - no real logic is needed, so I just did. LWP::Simple gave me most inspiration for this module. I usually have it export get and $ua, but I also often use a get and an $ua myself (yes, I do mix LWP::Simple with full blown LWP::UserAgent stuff). It's how I thought of the prefix. It's a shame we use exporters instead of importers, really.
Why isn't Exporter::VA on CPAN yet? I don't know. The powers that be seem to be slow and/or not very clear. It's in my directory, just not indexed.
That's probably because you used a zipfile. Try distributing the module as a gzipped tarball instead. If you use FTP, make sure you upload using binary transfer, not ascii.
I no longer believe in module registration. I registered all of my modules, and none is in the (still manually maintained) module list. Did not get any response at all. Doesn't matter much, since everyone uses search.cpan.org and/or CPAN.pm or CPANPLUS anyway, and modules get added to that index automatically.
- Yes, I reinvent wheels.
- Spam: Visit eurotraQ.
In reply to Re: Re: Re: Re: Re: Re: (bbfu) (Exporter::VA) Re: Exporter::Dream
by Juerd
in thread Exporter::Dream
by Juerd
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |