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.

In reply to Re: Re: Re: Re: (bbfu) (Exporter::VA) Re: Exporter::Dream by Juerd
in thread Exporter::Dream by Juerd

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.