In specific, Exporter::VA will do everything Exporter::Dream does, except for automaticly creating the :all tag. It also has the advantage of already exsiting, and doing pretty much anything you'd want an Exporter to do.

It's a huge exporter with lots of options, various prefixes and (imho) unclear syntax. Although it does indeed do much of what Exporter::Dream does, I think the two can happily live together (I hope ::VA will get something like _prefix too. It's trivial to implement, and makes things much nicer). I'm not after versioning or configuration through the import method, especially not with v-strings :).

You say Exporter::VA has the advantage of already existing. While that is true, it is of not much use until it is uploaded to CPAN. You used a cpan:// link, so you probably thought it was already there. Either it is not, or search.cpan.org is broken.

- Yes, I reinvent wheels.
- Spam: Visit eurotraQ.

I don't recal you commenting on the syntax when ::VA was in the design phase -- JMD requested comments quite a bit. You're right, though -- it would be nice if ::VA did _prefix. As to the versioning, it's optional -- just set the default version equal to the current version. As to configuration, I assumed you /did/ want it because you explicitly pointed it out that it won't do it, and said it would be nice if it did (or at the very least, /asked/ if it would be nice if it did).

---

Warning: Unless otherwise stated, code is untested. Do not use without understanding. Code is posted in the hopes it is useful, but without warranty. All copyrights are relinquished into the public domain unless otherwise stated. I am not an angel. I am capable of error, and err on a fairly regular basis. If I made a mistake, please let me know (such as by replying to this node).

I don't recal you commenting on the syntax when ::VA was in the design phase

I wasn't there to comment on it, or I wasn't interested at that time. Anyway, I don't think Exporter::VA should be changed. To support its numerous features, lots of syntax simply has to be there. Same goes for Perl: we have a lot of syntax, because otherwise we'd need a huge amount of words to implement the same functionality. It's just not as clean as I would like an exporter to be. There's not much wrong with @EXPORT and @EXPORT_OK and %EXPORT_TAGS either: it works, and what happens is obvious. It's just not as clean as I'd like it to be.

As to the versioning, it's optional -- just set the default version equal to the current version.

I think there should be an alternative that doesn't even provide versioning stuff. Too often, people will use every feature that is available, just because they can. See also subroutine prototypes.

Really, I have nothing against Exporter::VA, and would like to see it on CPAN (Why isn't it already?), and think multiple exporters can and *should* co-exist. Having alternatives is important when it comes to style :)

- Yes, I reinvent wheels.
- Spam: Visit eurotraQ.