At 7:56 PM -0600 11/29/07, John E. Malmberg wrote: >Craig A. Berry wrote: >> >>I've tried taking what's in Ken's repository and putting it in blead >>and it introduces several test failures. The most significant >>problem is that the new function VMS::Filespec::vms_realname returned >>garbage when passed a symbolic link. I've fixed the failure behavior >>with #32556, but it still fails and is not suitable for use in core >>modules just yet. > >Ok, that patch makes sense. But now do you understand that test using the >vms_realname or vms_realpath is still telling you the truth that the symbolic >link is not understood by the filesystem as a valid link.
I understand that the initial implementation of symbolic links on VMS only supports link targets in UNIX syntax, not native syntax, which seems odd, but that's the way it is. I could not get VMS::Filespec::vms_realname to succeed with a symbolic link regardless of whether the link target was in UNIX syntax (which is supposed to be supported) or VMS syntax (which I prefer to call unsupported, rather than invalid, as we're giving it perfectly valid native path names). No doubt using VMS::Filespec::vms_realname will be more efficient, more elegant, and enforce correctness more than what we have now, but not until it's debugged and working, which unless there's an unexpected thaw of suitable duration will be after 5.10. What we currently have in _vms_abs_path in blead doesn't care what syntax the link target is in as long as it's a valid path, and it seems to me it shouldn't have to care. Or, to move the problem upstream, cwd.t (or any other Perl program) shouldn't have to know that it needs to convert a path to UNIX syntax before symlinking to it. We may need to address that in our symlink() wrapper at some point. -- ________________________________________ Craig A. Berry mailto:[EMAIL PROTECTED] "... getting out of a sonnet is much more difficult than getting in." Brad Leithauser
