Actually, you might want to spend more time thinking about how your perl will run, not how it's written. If you are writing a CGI, you can use mod_perl on apache, Perl for Isapi on IIS, etc...

Also, I have found that using Perl2Exe can dramatically speed up a script that gets started often by eliminating the compile time.

I guess the point is that within reason, programming practice has a lot less to do with efficiency than run time implementation. Welcome to the world of interpreted languages.

That all said, use references, and avoid large hashes.

Hammy
Nothing4sale.org

In reply to Re: Re (tilly) 1: Efficiency and overhead of subs by HamNRye
in thread Efficiency and overhead of subs by stillinger

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.