Re: device name problems with extended charset and File::Spec

2009-06-02 Thread John E. Malmberg
Craig A. Berry wrote: On Jun 2, 2009, at 8:39 AM, John E. Malmberg wrote: John E. Malmberg wrote: The bug is in vms.c, not File::Spec. These two one liners demonstrate it: EAGLE> perl -e "print 'true' if -w '/sys$scratch'" EAGLE> perl -e "print 'true' if -w 'sys$scratch:'" true Someth

Re: device name problems with extended charset and File::Spec

2009-06-02 Thread Craig A. Berry
On Jun 2, 2009, at 8:39 AM, John E. Malmberg wrote: John E. Malmberg wrote: The bug is in vms.c, not File::Spec. These two one liners demonstrate it: EAGLE> perl -e "print 'true' if -w '/sys$scratch'" EAGLE> perl -e "print 'true' if -w 'sys$scratch:'" true Something is wrong with the

Re: device name problems with extended charset and File::Spec

2009-06-02 Thread John E. Malmberg
John E. Malmberg wrote: Craig A. Berry wrote: With current blead, if I define both DECC$EFS_CHARSET and DECC$EFS_FILENAME_UNIX_REPORT, I see the following: $ perl -"MFile::Spec::Functions" -e "print catfile(File::Spec->tmpdir(), 'bar');" ./bar Obviously it should be giving me '/sys$scratch/

Re: device name problems with extended charset and File::Spec

2009-06-02 Thread John E. Malmberg
Craig A. Berry wrote: With current blead, if I define both DECC$EFS_CHARSET and DECC$EFS_FILENAME_UNIX_REPORT, I see the following: $ perl -"MFile::Spec::Functions" -e "print catfile(File::Spec->tmpdir(), 'bar');" ./bar Obviously it should be giving me '/sys$scratch/bar'. With only DECC$EFS