in reply to Recommendation for dynamically "using" modules

If you think you need to load+export, and you don't know how, that is strong hint (certainty) that you don't need to do this (you're doing it wrong, exporting is the devil)

Module::Load,

perl5, perl5::ingy
ToolSet
Syntax::Collector
Toolkit
rig
see perlrun#PERL5OPT , PERLLIB, PERL5LIB
sitecustomize under perlrun#* f*
how to make lexical pragma global, hints ( pl_hints $^H %^H ), taint::all, Re: batch 'use' possible? (perl5.pm Toolset.pm, Syntax::Collector , Toolkit.pm, rig.pm, sitecustomize.pl, PERL5OPT )( load multiple commonly-used favorite modules in a single import expression )

export into / Import::Into

 

:D

  • Comment on Re: Recommendation for dynamically "using" modules (export import into)

Replies are listed 'Best First'.
Re^2: Recommendation for dynamically "using" modules (export import into)
by daxim (Curate) on Jul 11, 2013 at 08:05 UTC
    Thanks, Anonymonk! I'm going to steal this list for my talk at YAPC.
[reply]
Re^2: Recommendation for dynamically "using" modules (export import into)
by McA (Priest) on Jul 11, 2013 at 08:17 UTC

    Thank you for that fast reply.

    I totally agree to your statement, especially to

    "[...] exporting is the devil [...]"
    , but probably it can help to do a transition in an existing code base. Sometimes you have to do changes step by step.

    I did find modules for the "loading" part, but not for the "exporting" to a level above the function doing the module load. Import::Into looks interesting.

    Best regards
    McA

[reply]
[d/l]

In Section Seekers of Perl Wisdom