There is less overhead than storing data in a separate file.
No seek necessary because the filehandle is already at
the right position after the script compilation.
Also, if
your data section is very long and never explicitely
accessed using the
DATA handle, it will
never be loaded from the disk (except the beginning
by normal read-ahead of the OS).
In fact if you "rewind" it by seek( DATA, 0, 0) than do print <DATA> you do print the whole script:
seek( DATA, 0, 0);
print <DATA>;
__DATA__
this is no quine but downright cheating
|
note to refute a remark on the CB
To my own surprise: you can pipe this script to Perl and you will get the same result as executing it from a file because of the IO buffering.
Indeed, the perl seek() does not translate on a seek() system call. So, if buffering permits, you can perl-seek a non seekable stream!!!
quine page
-- stefp
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.