Testing W32 files names w/spaces:

#!/usr/bin/perl
use strict;
use warnings;

my $fullelementpath = "f:/_wo/haldane.txt";
if (-T $fullelementpath) {print "passed T\n";}else{print "failed for $
+fullelementpath\n";}
# -----------------------
my $fullelementpath2 = "f:/_wo/haldane space.txt";
if (-T $fullelementpath2) {print "passed T\n";}else{print "failed for 
+$fullelementpath2\n";}

[download]

Output:

C:\>pl_test\887602.pl
passed T
passed T

C:\>

[download]

In reply to Re^2: File test -T (text) and quoted filenames by ww
in thread File test -T (text) and quoted filenames by AdamtheKiwi

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.