• You should be able to specifiy hard references instead of symbol names. (Together, these two would let you avoid having any globals if you want -- and I want.)
• Resolve the conflict I just created with exporting arrays and code via the reference syntax and the tag and \&figure_it_out syntax. (I really think that you should be able to export via hardrefs rather then symbolic refs, though.)

I didn't do hard refs because of this conflict. I suppose you could say foo => sub { \&foo_hard } with the existing design. Any other design (additional decorations of some kind?) would need to be at least this simple.

• You shouldn't have to have %EXPORTER as a global (use vars, our) variable. Instead (or additionaly), you should be able to pass a hashref (or just a hash?).

You mean right in the use line, like

use Exporter::VA (foo => 'foo_internal');
[download]

• Perhaps you could autogenerate the direct-callable functions (IE create a sub foo{} that calls the correct foo_old or foo_new, if sub foo doesn't exist).

Wonderful. An inherited AUTOLOAD would do the trick.

• Instead of having that single function call in what is otherwise a purely declarative API, have a key value of '' mean "symbol name same as export name".

I suppose that would be OK. Also, a special hash entry could list all the non-alias simple exports, instead of using a function call.

• Document that pragmata imports traditionaly begin with a - and can be implemented using \&figure_it_out.

Sure. Is there any prior art on pragmatic imports other than version numbers?

• $EXPORT_DEFAULT_VERSION should be doable in the hash too, rather then as a seperate global. (Perhaps _Exporter_VA_defaultVersion.) Also, if it's not given, it should default to $VERSION, not have no default.

If not given, default to the same version number as the Exporter::VA's version? I don't get it.

Everything in the hash: Sure could. But I think it should be clearer than that.

Thanks for your thoughts. That was all very useful feedback. Stay tuned for the next iteration.

—John

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.