On Dec 6, 2005, at 11:46 AM, John E. Malmberg wrote:
Ken Williams wrote:
Hi John,
Thanks for the patch, I've applied it. Could I trouble you to also
add a few tests to Spec.t to exercise these dead bugs?
Someone already did with a recent change to Spec.t, which made them
show up as failed at the same time I made a significant change to
vms.c, so I had to chase down what happened.
Oh, okay. Thanks.
Or do you want some tests to expose the bugs in processing '^'
characters in OpenVMS file specifications? Those file specifications
will not exist on the VAX platform, so it may not be appropriate to
run the tests on them.
I was thinking we could add those as TODO tests, but I was unaware of
the problems with VAX legacy stuff. Do you think the differences
between the two platforms are significant enough to merit a separate
File::Spec subclass for one of them?
One way or another though, if we're going to add '^' processing on VMS
we'll need tests for it.
By the way, canonpath('./') on OpenVMS returns '[]' instead of a UNIX
format string. I have not had time to test what a real UNIX/LINUX
system is expected to return.
I'd expect that to return '.'.
Proper functioning of lib/File/Spec/VMS.pm and CWD.pm require that
they know what mode that the OpenVMS CRTL is in for handling UNIX
format file specifications and ODS-5 extended character sets.
That sounds a little scary. What's a CRTL?
-Ken
