Yes, using pipes is the right way. I am doing that quite frequently, for example sorting a huge file with the shell sort command and redirecting the sorted output to a Perl program through a pipe. At the beginning, sort is not writing anything out (it has to process at least in part the whole file before it can start printing out anything); during that phase, the Perl program is just sitting idle, waiting for data to start to come. At a later point, the sort command might be spitting out data lines faster than the Perl program would be able process them, but it is OK because the pipe pauses the sort to enable the Perl program to consume the data at its own speed.
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.