Nicholas Clark wrote:
On Mon, Aug 27, 2007 at 08:26:33PM -0500, John E. Malmberg wrote:
John E. Malmberg wrote:
But perlfunc says VMS can do whatever it feels is right:
Behavior of this function varies wildly depending on your system
implementation. For example, it will usually not work across file system
boundaries, even though the system I<mv> command sometimes compensates
for this. Other restrictions include whether it works on directories,
open files, or pre-existing files. Check L<perlport> and either the
rename(2) manpage or equivalent system documentation for details.
So I don't know. I don't use VMS, so I don't know what seems sensible.
The change was checked in a while ago.
The C<rename> on VMS now follows UNIX behavior, and will rename
directories the same way.
There is also a currently undocumented option that will convert both the
C<unlink> to remove all versions, and C<rename> to result in only one
version of the new file and no versions of the old file.
Hopefully soon I can start working on the API to expose reading and
setting the VMS behavior options, both so that tests can be made for
them, and so that tests and library modules will behave as the the
current VMS behavior desires.
-John
[EMAIL PROTECTED]
Personal Opinion Only
