- <*.txt> vs. glob '*.txt':
Depends. A neat trick i lifted from merlyn is to use
File::Find to find your target files and push them to
@ARGV via:
push @ARGV, $File::Find::name if /MAGIC_CONDITION/;
then you can modify their contents via the empty angle
brackets: <>. I don't think you can do that
with glob ...
- readline over angle brackets:
I tend to use angle brackets - guilty of lazy typing. ;)
- backticks
I try to avoid them anytime i can. When i first started
using Perl i used them a lot. Too much. Then i found
system and exec, and IO::Pipe among other CPAN modules
that can replace backticks.
All in all, i think a good exercise is to force yourself
to practice The Other Way. Not necessarily in your
production code, but in the throw-away scripts that you
write from time to time. Balance is good. :)
jeffa
L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
B--B--B--B--B--B--B--B--
H---H---H---H---H---H---
(the triplet paradiddle with high-hat)
-
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.
|