This might actually be due to the version of
File::Spec being used by FindBin. I see that FC2 uses version 1.5 of File::Spec::Unix, whereas Redhat 9 (Shrike) uses 1.4. Here's a subset of the diff:
< $VERSION = '1.5';
---
> $VERSION = '1.4';
>
> use Cwd;
72,73c74,79
<
< $self->canonpath(join('/', @_, '')); # '' because need a trailin
+g '/'
---
> my @args = @_;
> foreach (@args) {
> # append a slash to each argument unless it has one there
> $_ .= "/" if $_ eq '' || substr($_,-1) ne "/";
> }
> return $self->canonpath(join('', @args));
85c91
It would appear that the trailing slash is considered more "correct" but was not functioning correctly in the older version?
At any rate, if you use the catfile() and catdir() methods from File::Spec, the dreaded '//' problem should not be an issue.
Matt
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
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:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.