Michael G Schwern wrote:
On Sat, Jul 09, 2005 at 01:53:36AM -0400, John E. Malmberg wrote:
Hmm. Here's the easiest of my failures to analyze:
not ok 52 - vmsify('.../'): '[....]'
# Failed at ../vms/ext/filespec.t line 24
# got '[....]'
# expected '[...]'
It also should be expected to return "[.^.^.^] if the logical names
%ENV{$DECC$FILENAME_UNIX_REPORT} and %ENV{DECC$EFS_CHARSET} are defined
to "1" or their first letter is "E" or "e"
[.^.^.^.] is a legal directory on an ODS-5 volume.
Missing the point. The point is I'm running different code on Unix than
you are on VMS.
I did not miss the point.
I am currently running different code on VMS than anyone else :-)
The QTV (internal OpenVMS Quality-Test-Verification) group has not
blessed it yet on IA64 for an unreleased version of OpenVMS that is also
in test.
I think I can start submitting some off the patches needed that will
likely be stable while getting the final issues resolved. Some of the
issues involve fixing a future CRTL.
vms/ext/Filespec.pm is out of date and broken.
And my point that you missed is:
So is Perl on OpenVMS when dealing with OpenVMS ODS-5 file
specifications. Filespec.pm is just more broken than the rest.
I am just giving a heads up in case that someone is working on fixing
Filespec.pm that even bringing it up to what is currently in the VMS C
source is still not going to make it correct.
What is probably needed is some way for VMS to be able to run
Filespec.pm with out the overrides from the extension present in the tests.
-John
[EMAIL PROTECTED]
Personal Opinion Only
