There is nothing special about new; it's just an often-used name for constructors. After all, this isn't C++ or Java.

As far as autouse, all it does is to make stubs in the proper packages that will load the module if it isn't loaded. And you have to name the routines that you want to make stubs for. So assuming that the first subroutine that you call in your module is always "new", and that you aren't exporting anything from your module, it should be sufficient to do:

use autouse 'MyModule' => 'MyModule::new';
So that you'll get MyModule loaded when you go:
my $mym = MyModule->new();
Of course, if you call any other routines in your module first, they'd have to be added to the autouse list.

Subsequent accesses to methods (subroutines) defined in MyModule will work fine after the first one causes the autoload.


In reply to Re: use autouse with OOP by bikeNomad
in thread use autouse with OOP by DBX

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.