In vmsperl.pod, VMS 8.3 is real, and not future, and the restrictions
about the decc features have been removed.
Document that symbolic link targets must be in Unix syntax, and that a
path to the target from the POSIX root needs to exist.
In perlport.pod,
Clarify some issues on the %ENV hash for VMS, and document that symlink
is now available on VMS, and that on VMS it requires Unix syntax targets.
-John
[EMAIL PROTECTED]
Personal Opinion Only
--- /rsync_root/perl/pod/perlport.pod Sat Nov 24 03:08:22 2007
+++ pod/perlport.pod Sun Nov 25 19:35:10 2007
@@ -433,6 +433,16 @@
VMS the C<%ENV> table is much more than a per-process key-value string
table.
+On VMS, some entries in the %ENV hash are dynamically created when
+their key is used on a read if they did not previously exist. The
+values for C<$ENV{HOME}>, C<$ENV{TERM}>, C<$ENV{HOME}>, and C<$ENV{USER}>,
+are known to be dynamically generated. The specific names that are
+dynamically generated may vary with the version of the C library on VMS,
+and more may exist than is documented.
+
+On VMS by default, changes to the %ENV hash are persistent after the process
+exits. This can cause unintended issues.
+
Don't count on signals or C<%SIG> for anything.
Don't count on filename globbing. Use C<opendir>, C<readdir>, and
@@ -2031,7 +2041,10 @@
=item symlink
-Not implemented. (Win32, VMS, S<RISC OS>)
+Not implemented. (Win32, S<RISC OS>)
+
+Implemented on 64 bit VMS 8.3. VMS requires the symbolic link to be in Unix
+syntax if it is intended to resolve to a valid path.
=item syscall
--- /rsync_root/perl/vms/perlvms.pod Fri Oct 5 00:40:35 2007
+++ vms/perlvms.pod Sun Nov 25 18:44:47 2007
@@ -593,11 +593,10 @@
statvfs, socketpair
-The following functions are expected to soon be available on Perls built
-on 64 bit OpenVMS 8.2 or later with the RMS Symbolic link package. Use
-of symbolic links at this time effectively requires the
-DECC$POSIX_COMPLIANT_PATHNAMES to defined as 3, and operating in a
-DECC$FILENAME_UNIX_REPORT mode.
+The following functions are available on Perls built on 64 bit OpenVMS 8.3.
+The target for a symbolic link needs to be in Unix format if it is intended to
+resolve to a valid path. The POSIX root must also be set up and there must be
+a path from that POSIX root to the symbolic link target.
lchown, link, lstat, readlink, symlink
