in reply to Re: How should this work ? (design of Exporter::VA)
in thread How should this work ? (design of Exporter::VA)

I like that. I was thinking of a "suppliment" keyword or somesuch that would be for subsequent invokations, but I like the semantics of "only". It would suppress setting up the direct-call autoload hooks, or prevent conflict if used subsequently.

The import pragma switches are double-dashed. If you don't define them, they are inherited from Exporter::VA to control the export process itself. So I'd say use Module v1.2 qw/ --only baz /;.

Looking at tye's reply, what would you name a switch that does the opposite, that is, enables the AUTOLOAD hook to allow direct calls to the module to be versioned?

—John

Replies are listed 'Best First'.
Re: Re: Re: How should this work ? (design of Exporter::VA)
by traveler (Parson) on Dec 18, 2002 at 23:05 UTC
    what would you name a switch that does the opposite, that is, enables the AUTOLOAD hook to allow direct calls to the module to be versioned?

    I had a bit of trouble parsing this. Do you mean setting a default version for calls to functions that aren't explicitly exported? If that's what you mean, I wouldn't do it. I look at the versions in reverse order of being used.

    If I'm not understanding, could you give an example?

    --traveler

[reply]
[d/l]

In Section Seekers of Perl Wisdom