Hi,
Copying a non-existing file with file.copy creates an empty file
> r <- file.copy("non-existing-file", ".")
> r
[1] TRUE
... and returns TRUE!
Now, when used in "vectorized" mode
> r <- file.copy(c("toto1", "toto2"), c("dest1", "dest2"))
[1] FALSE FALSE
file.copy looks much more reasonable, except that files "dest1"
and "dest2" are still created (despite the fact that "toto1" and
"toto2" don't exist).
If the 'to' argument is not a dir:
> r <- file.copy(c("toto3", "toto4"), ".")
> r
[1] TRUE TRUE
!!?!?
May be those are (undocumented) features, but I bet 99.9% of the users would
expect something different...
Cheers,
H.
file.copy
2 messages · Hervé Pagès, Henrik Bengtsson
FYI: I reported this to r-devel on July 23, 2006: http://tolstoy.newcastle.edu.au/R/devel/06/07/6220.html There was no follow up. /Henrik
On 1/17/07, Herve Pages <hpages at fhcrc.org> wrote:
Hi, Copying a non-existing file with file.copy creates an empty file
> r <- file.copy("non-existing-file", ".")
> r
[1] TRUE ... and returns TRUE! Now, when used in "vectorized" mode
> r <- file.copy(c("toto1", "toto2"), c("dest1", "dest2"))
[1] FALSE FALSE file.copy looks much more reasonable, except that files "dest1" and "dest2" are still created (despite the fact that "toto1" and "toto2" don't exist). If the 'to' argument is not a dir:
> r <- file.copy(c("toto3", "toto4"), ".")
> r
[1] TRUE TRUE !!?!? May be those are (undocumented) features, but I bet 99.9% of the users would expect something different... Cheers, H.
______________________________________________ R-devel at r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel