Trying to use autoload for the first time ;-)

I can create a "sub AUTOLOAD" in main:: to dynamically call a function and it works cool!

Now, I want to move the stuff into a package called foo::

But, the docs say (I think) that there can only be one sub AUTOLOAD defined in each package...I was thinking I could use BEGIN in my package to create the main::AUTOLOAD to do what I want...but this assumes that the user hasn't already created a main::AUTOLOAD....I am stuck

(pseudo code) 
package main;
  myfunc(1,2,3); # I want to redirect to foo::myfunc()

  sub AUTOLOAD { 
    if $caller eq "foo"
       foo::myfunc(@_);
  }  
  # Any way to get rid of the main::autoload and somehow
  # handle it in the foo package ???  Or is there a way 
  # to override AUTOLOAD in my package using BEGIN or ???

[download]

thanks!!!

uc(autoload) in title - dvergin 2002-05-11

In reply to AUTOLOAD and packages by smackdab

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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! —
  • 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:
    & &amp;
    < &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.