- 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');
- 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