comment on

The "second-best" thing I do regularly is to use path strings instead of building them with the File::Spec functions. It's all ActiveState's fault: their version of Perl for Win32 lets me get away with using open my $FH, '<', './data/source.txt' or die($!), where as other Win32 versions of Perl will not DWIM on the forward slashes.

This has bitten me more than once when one of the scripts I write for work gets run on a box using PXPerl...

<-radiant.matrix->
A collection of thoughts and links from the minds of geeks
The Code that can be seen is not the true Code
"In any sufficiently large group of people, most are idiots" - Kaa's Law

In reply to Re: RFC: Perl Second-Best Practices by radiantmatrix
in thread RFC: Perl Second-Best Practices by dimar

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.


P is for Practical
	PerlMonks