Obviously, obviously ...
The essential point of my thread was of course not a quibbling as to the actual byte-size of “the language-compiler/runtime component,” but rather to emphasize that “the language-compiler/runtime component,” ... nor any low-level details of its implementation ... “is not the real point here.” Every bit of that “plumbing” is just A Means To An End, and in any case it is a minuscule portion of the total body of source-code that is of professional interest to me. In the long run, I don’t really care if, say, DBI “runs x% faster.” But I do rather-profoundly care that it continues to pass 100% of its thousands of tests.
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, 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, 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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
|
|