You're using "/" for paths. Many devs are running Cat on Windows. You just broke their applications. :) Path::Class is guaranteed to be there for Cat stuff.

What about Catalyst causes it to break on Windows from using a solidus for paths? Most applications have no problem using it on Windows. IIRC the system internally even supports it, although the command interpreter does not. In any case, I've been using '/' as a path separator on Windows for years. 

perl -e "print $_ . qq{\n} for glob q{'c:/documents and settings/*'}"

[download]
perl -e "opendir my $d, 'c:/documents and settings'; print $_ . qq{\n}
+ for readdir $d;"

[download]
perl -e "open my $f, '<', $ENV{systemdrive} . '/windows/system32/drive
+rs/etc/hosts'; print $_ while <$f>;"

[download]
perl -e "$ENV{PATH} = 'c:/windows/'; system( 1, 'notepad.exe', 'c:/win
+dows/system32/drivers/etc/hosts' );"

[download]

You might notice that last one is an example of the system using a path with '/' to find an application and launch it and that program using its argument with '/' as the separator to open the file. It's not subject to any special reworking by the Perl runtime.

Having a portable path-handling library helps with platforms like MacOS Classic, VMS, and others. Any version of Windows that's still getting security updates from MS shouldn't need any special treatment for the path separator, though. That volume enumeration by letter in the paths is still oddball these days, but that's supposed to go away in the near future.

If an application on Windows is broken by a path with '/' as the separator, there's a problem, IMO, in that application. The Windows CLI itself gets excused for mistakes of the past. Even it does the right thing with proper convincing: 

dir "c:/windows/system"

[download]

In reply to Re^2: [RFC: Catalyst::Plugin::AutoValidate] Easy request parameter validation with Catalyst by mr_mischief
in thread [RFC: Catalyst::Plugin::AutoValidate] Easy request parameter validation with Catalyst by holli

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.