2009/9/25 Niko Tyni <nt...@debian.org>:
> On Fri, Jul 25, 2008 at 09:22:26PM +0100, Reuben Thomas wrote:
>> Package: perl-doc
>> Version: 5.8.8-7etch3
>> Severity: minor
>>
> Quoting the whole paragraph:
>
> The system copy routine may also be called directly under VMS and OS/2
> as "File::Copy::syscopy" (or under VMS as "File::Copy::rmscopy", which
> is the routine that does the actual work for syscopy).
>
> This parses as "VMS => you can use either syscopy or rmscopy to access the
> system copy routine; OS/2 => just syscopy does this". This interpretation
> seems to match the actual code.
In that case, I suggest clarification. Re-reading the entire
description of syscopy, I think it can be simplified, because it
currently contains unnecessary repetition. In particular, the sentence
you quote largely repeats earlier parts of the description.
Hence, I suggest deleting the paragraph:
The system copy routine may also be called directly under
VMS and OS/2 as
"File::Copy::syscopy" (or under VMS as
"File::Copy::rmscopy", which is the routine that
does the actual work for syscopy).
and changing the first paragraph of the syscopy description to:
syscopy
File::Copy also provides the "syscopy" routine, which
copies the file specified in the
first parameter to the file specified in the second
parameter, preserving OS-specific
attributes and file structure. For Unix systems, this is
equivalent to the simple "copy"
routine, which doesn’t preserve OS-specific attributes.
For VMS systems, this calls the
"rmscopy" routine (see below), which you can also call
directly. For OS/2 systems, this calls the "syscopy" XSUB directly.
For Win32 systems, this calls "Win32::CopyFile".
(i.e. add the information that you can call rmscopy directly).
> I don't see a bug here,
The bug is that it took you to explain it to me (and check with the
code to be certain)!
--
http://rrt.sc3d.org
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
