Beefy Boxes and Bandwidth Generously Provided by pair Networks
Think about Loose Coupling

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
> The other easy option is to split the POD from the code and store it elsewhere. Yes, that's something I've often pondered, but you end up with two versions and the ensuing hassle. Software is just a side-dabble for me, so my knowledge of real-world issues is limited, esp when a team is involved. The popularity of other interpreted languages for CGI - PHP for example - and apparent popularity of attempted Perl compilers some years back has always made me curious as to any real-world benefits of such measures. In the modern world of huge RAM and lightning-fast CPUs there's probably none, but a knowledgable comment or two from someone with experience in that area would slake decades of merely wondering.

In reply to Re^2: Performance penalties of in-Perl docn vs compiled CGIs. by phirun
in thread Performance penalties of in-Perl docn vs compiled CGIs. by phirun

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

  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.