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).
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
