Does anyone have insight into this situation? On one Windows 2003 server
system, backslashes in path names in arguments to Perl are getting translated
to forward slashes. On other Windows 2003 systems, with the exact same version
and build of ActiveState Perl installed, the conversion to forward slashes does
not happen. I've checked the PATH and the file associations. Perl is in all
cases coming from C:\Perl\bin\perl.exe. I examined the registry entries in
HKLM\SOFTWARE\ActiveState, and they are all identical.
The weird thing is, the Perl on this machine behaved like the Perl on all the
other machines until some time in the middle of last week. Then it changed.
Drove me crazy for a couple of days until I wrote the following test case and
verified the new behavior.
TIA,
Marilyn Sander
>type tryperl.pl
for $i ( 0.. scalar(@ARGV) -1 ) {
$arg=$ARGV[$i];
print "argument $i is $arg\n";
}
>perl tryperl.pl E:\test_downloads H:\no_such_directory D:/whatever
argument 0 is E:/test_downloads
argument 1 is H:/no_such_directory
argument 2 is D:/whatever
>perl -v
This is perl, v5.8.8 built for MSWin32-x86-multi-thread
(with 21 registered patches, see perl -V for more detail)
Copyright 1987-2006, Larry Wall
Binary build 816 [255195] provided by ActiveState http://www.ActiveState.com
Built Mar 1 2006 18:00:52
Perl may be copied only under the terms of either the Artistic License or the
GNU General Public License, which may be found in the Perl 5 source kit.
Complete documentation for Perl, including FAQ lists, should be found on
this system using "man perl" or "perldoc perl". If you have access to the
Internet, point your browser at http://www.perl.org/, the Perl Home Page.
--
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
http://learn.perl.org/
