foreach my $pwd (split(/\\/,'\foo\foo1\foo2')) {
[download]

Change the line to read:

foreach my $pwd (split(/\\/,'\foo\foo1\foo2')) { ...
[download]

Update: The following code (as per above, but with an output):

foreach my $pwd (split(/\\/,'\foo\foo1\foo2')) {
    print $pwd, "\n";
}
[download]

__OUTPUT__

foo
foo1
foo2
[download]

foreach my $pwd (split('/\/\','/\foo/\foo1/\foo2'))
[download]

perl -e " print join(', ',split(/\\\\/,'\foo\foo1\foo2'))"
, foo, foo1, foo2
[download]

I got this working on the command line like you have in your example, and it works, but in my script it's still not working. Very strange

I got this working on the command line ... but in my script it's still not working

I'm not positive, but I'd say the shell is eating one pair of backslashes. Basically, the shell sees \\\\, passes it in to perl as \\, which gets passed into the RE engine as \. Welcome to the backwhack hell that is multiple layers of interpolation. :)

So, in summary, \\\\ on the shell should be \\ in your script.

>echo $perlcode
$a="x\\y\\z";@b=split('\\\\',$a);print join(";",@b),"\n"
>perl -e "$perlcode"
x;y;z
[download]

>echo $perlcode
$a="x\\y\\z";@b=split("\\\\",$a);print join(";",@b),"\n"
>perl -e "$perlcode"
x;y;z
[download]

Maybe some wise monk would enlighten us?

Sandy

Single quoted type strings do treat \\ and \ followed by the ending delimiter character as special, just as double quoted strings do. It's everything else that they don't treat specially.

Ah HA!

Thanks.