Beefy Boxes and Bandwidth Generously Provided by pair Networks
Welcome to the Monastery

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
Hey, thanks for a most thoughtful and informative reply, bliako. Yes, I figured that I was asking the sort of "dumb question" inevitable for amateurs and dilettantes in any subject. I've always regarded Perl as a major intellectual accomplishment, and its internal complexity and inner convolutions make traditional compilation far more difficult than the simplistic assumptions of my question, if I understand you correctly.

So be it! Once written in Perl, it stays in Perl! I can live with that. And the analogue of Sisyphus describes VERY nicely my own view of coding as a profession, which is why I went with hardware. So no, NO WAY am I intending to "go this way". Simply lack the courage.

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.