Michael G Schwern wrote:
I'm examining the feasibility of making VMS::Filespec available to all
installations (makes testing File::Spec::VMS a whole lot easier) and
ran vms/ext/filespec.t on my OS X box. I got some failures but none
of them seem to be related to my running on Unix. They all appear to be
genuine bugs in the code.
So... has anyone run ext/vms/filespec.t on VMS in a while?
Quite a bit, except for this past week while I am on vacation.
It is producing incorrect answers when ODS-5 file specifications are in
use. Other wise known as Extended File Specifications or EFS.
Under ODS-5 file specifications, the UNIX path of "./.../foo" should be
translated to "[.^.^.^.]foo." in VMS.
Other translations that the script assumes should fail will not when
translated to legal ODS-5 specifications.
I think it was the one test script that I could not find an easy way to
make work when the OpenVMS CRTL was working in a UNIX report or the
comming Posix compliant pathname mode.
Is anyone on this list using the test RMS Symbolic links SDK?
I am going to have a lot of gnu diff files to post soon. Should I send
them to this list an order that they can be applied harmlessly or put
them all in a .ZIP archive somewhere?
I had to do a lot of work in the Makemaker routines to get them to pass
the tests when the OpenVMS CRTL is by default returning names in UNIX
syntax instead of VMS.
-John
[EMAIL PROTECTED]
Personal Opinion Only
