If I want to form a consistent path (say: Unix style), then I need to translate the backslashes in the user-supplied path to forward slashes.

(My original reply has already been downvoted ... which is not a good sign ... though that depends upon who downvoted it, and why.) On windows, I generally find that it doesn't matter whether the user supplies / or \ as the path separator. For example, this works fine for me on windows (where the /_32/pscrpt/inline folder exists):

use strict;
use warnings;
use Cwd;

my $path = '/_32/';
my $user_supplied = 'pscrpt\inline';

my $ok = chdir($path . $rel);

print $ok, "\n", getcwd(), "\n";
__END__
prints:
1
C:/_32/pscrpt/inline
[download]

In this case there's clearly no need for you to translate the backslashes to forward slashes. (I imagine that on Unix, however, things might be a little different :-)

Other examples are: Translating a Unix path to Windows (for usage in a generated BAT file)

Windows bat files will recognise the forward slash as a path separator ... at least that was the case for my test. (My test was to add "C:/b" to the path via a bat file, then check that an executable in C:/b ran, even though C:/b was not my cwd.)

Cheers,
Rob

---

---

• 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.