Re: device name problems with extended charset and File::Spec
"John E. Malmberg" <[email protected]>
| Newsgroups | gmane.comp.lang.perl.ports.vms |
|---|---|
| Message-ID | <[email protected]> |
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
>>> Something is wrong with the stat code. I will try to look at it
>>> tonight.
>>
>> To be more precise, the problem has to be in the perl_cando code.
>>
>>> In file::spec->_tmpdir() the -w test is used to make sure that the
>>> temp directory is writable, and it falls back to "." if it can not
>>> find one of '/tmp', '/sys$scratch', or $ENV{tempdir} as writable.
>
>
> Thanks. The blead build is currently broken so don't synch first.
> Hopefully we'll get it all sorted out soonish.
I am glad that I did not. I am running a test build now.
It was in the EFS internal version of vmsify("/SYS$SCRATCH"). It was
incorrectly translating it to "SYS$SCRATCH:[000000]".
I am a bit surprised that this did not show up sooner. In addition to
the patch to VMS.C, I need to add a test for this.
-John
[email protected]
Personal Opinion Only