Nonsense! Not every OS uses the forward slash (/) as path separator.

So what, the OP doesn't have one of those

On a classic, non-X MacOS, you will fail miserably because MacOS uses single colons (:).

No you won't, you'll get a nice error message, and then you cheerfully fix it -- or it will cheerfully work and you'll get a file with slashes in the name -- no misery anywhere

Same game, different rules with VMS ...

Same ol' same ol'

File::Spec is not perfect, but it still is better than simply using the forward slash everywhere.

File::Spec is great, Path::Class is better, but using forward slashes on unix/linux/windows will work 99% of the time

In reply to Re^6: DBD::CSV::prepare() problems by Anonymous Monk
in thread DBD::CSV::prepare() problems by polelo

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.