I really dislike downvoting (which I just did) on nodes expressing opinion; the more so, in this case, because all but fenLisesi's second sentence have merit (IMO). My error!
Update: The above was well intentioned, but bleary-eyed /me carelessly missed the typo in prop's OP, in which
find{ sub $total_size += -s if -f}, '.');
should be
find (sub { $total_size += -s if -f}, '.');.
mea culpa and apologies.
But sentence 2 amount to a direct and gratuitous negative implication about props' integrity (or, I suppose, ability to copy code from a book)... and it is wrong.
The intial code fragment comes from p71 of Intermediate Perl, 2nd edition. It is verbatim, save for the book's inclusion of a use File::Find above. And it's available, on line, for your ease of checking these assertions, at http://safari.oreilly.com/ (more precisely, and as a link, 7.4 . Closures)
-
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.
|
