There can be a significant perfomance penalty for using AUTOLOAD on OOP get/set functions however. It really depends on the objects purpose. We had some get/set routines autoloaded for database objects. So a autoloaded get/set function would get called for each record of each row that got returned, and it sucked majorly. By removing the autoloading and just accessing the data structure directly we increased the peformance by over 20 times (over a minute to about 3 seconds).

But AUTOLOADING is great for objects where the get/setting is not a significant process. And I love it for those lazy days of hacking out proof-of-concept stuff in the OOP world.

In reply to RE: autoload and selfload by perlmonkey
in thread autoload and selfload by jlistf

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.