The only reason to read the original file line by line would be that it's very large...
Surely not the "only" reason. Here are five other possible reasons, just off the top of my head. You might use a line-by-line approach:
- to allow the application to be used interactively
- to allow the application to be used as part of an unbuffered pipeline
- to minimize memory usage even on small inputs, in an embedded (or otherwise memory-limited) environment
- to restrict the tranformation to transforming individual lines (perhaps for backwards compatibility with a previous utility)
- Because the input data is always runtime-generated (or highly volatile in some other way), so rerunnability doesn't matter
Note that I don't disagree with you that using temporary files is safer in general, if
you can afford the costs involved. After all, using temporary files is precisely what IO::Insitu does. I only question your argument that its possible to deduce the necessity for temporary files from the particular I/O characteristics of the original example (or from any piece of undocumented code for that matter).
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- 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
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||