in reply to Re^2: Generic/Variable/Dynamic Subroutines? (Not a redefine)
in thread Generic/Variable/Dynamic Subroutines? (Not a redefine)

> Would you be able to elaborate, or comment, on the benefits of using autosplit for autoload

If you are loading code from a slow disk autosplit is faster.

This used to be helpful 20 years ago. ...

Update

If compiling Perl code is slow, just autoloading on demand is faster

Again, this used to be helpful 20 years ago. ... ;)

Cheers Rolf
(addicted to the Perl Programming Language and ☆☆☆☆ :)
Je suis Charlie!

  • Comment on Re^3: Generic/Variable/Dynamic Subroutines? (Not a redefine) (updated)

Replies are listed 'Best First'.
Re^4: Generic/Variable/Dynamic Subroutines? (AutoReloader)
by shmem (Chancellor) on Aug 21, 2017 at 18:08 UTC
    If compiling Perl code is slow, only autoloading on demand is faster

    Again, this used to be helpful 20 years ago. ... ;)

    Well, it is still useful for... what was the buzzword again? ah. "Continuous Integration" 'tis named I guess, if you replace AutoLoader with AutoReloader (PerlMonks thread).
    (yes, shameless plug :)

    perl -le'print map{pack c,($-++?1:13)+ord}split//,ESEL'
      I don't doubt there are still useful cases, I'm using AUTOLOAD a lot.

      But autosplit was particularly useful when RAM, disk access and processor speed were bigger issues.

      I'm reluctant to explain a newbie how to use a rocket instead of the bus.

      Cheers Rolf
      (addicted to the Perl Programming Language and ☆☆☆☆ :)
      Je suis Charlie!

        I'm reluctant to explain a newbie how to use a rocket instead of the bus.

        The OP, from their OP, doesn't look like a newbie in perl, at all. Exploring all of perl takes a long time...

        perl -le'print map{pack c,($-++?1:13)+ord}split//,ESEL'