It was surprising to me, also, that one must add a "\n" to one's programs to see the output as it is printed. Typing 'perldoc perlfaq5' from the command line explains why.
It turns out that the need to add a "\n" is an artifact of Larry Wall choosing to write perl in C. Perldoc explains that
The C standard I/O library (stdio) normally buffers characters set to devices...Any time you use print() or write() in Perl, you go through this buffering...Serial devices (e.g., modems, terminals) are normally line buffered, and stdio sends the entire line when it gets the newline.
The more I learn about Perl, the more I think that to really know Perl one must know the language that Perl is written in, C. Moreover, I think that, even aside from portability problems, Perl would not have been Perl if Larry had chosen to write it in Lisp or Pascal. Much of what we think of as Perlish is really C-ish.
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.