[Rd] no internal function "int.unzip" in R 2.9 on Windows
Dear list,
Using R 2.9, I have the following error on Windows when I try using
.Internal(int.unzip(...)):
> .Internal(int.unzip("test.zip",NULL, "."))
Error in .Internal(int.unzip("test.zip", NULL, ".")) :
no internal function "int.unzip"
The same error also happens with R 2.10 but not on R 2.8. And it does not
happen with R 2.9 on Mac or Unix.
I have googled the error message but cannot find much.
Does anyone know if the way R calls unzip functions on Windows has changed
and if this is permanent?
I am sorry if I miss something obvious, but any suggestions on how I can
fix the problem?
I want to keep using int.unzip and not the utils function unzip because I
use its output afterwards in my script.
Best wishes,
Audrey
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] no internal function "int.unzip" in R 2.9 on Windows
Dear Duncan and Uwe,
Thank you for your prompt answers. I will have a look at the unzip
function and try to modify it to make it producing the output I want.
Cheers,
Audrey
> On 3/25/2009 11:42 AM, aud...@ebi.ac.uk wrote:
>> Dear list,
>>
>> Using R 2.9, I have the following error on Windows when I try using
>> .Internal(int.unzip(...)):
>>
>>> .Internal(int.unzip("test.zip",NULL, "."))
>> Error in .Internal(int.unzip("test.zip", NULL, ".")) :
>> no internal function "int.unzip"
>>
>> The same error also happens with R 2.10 but not on R 2.8. And it does
>> not
>> happen with R 2.9 on Mac or Unix.
>> I have googled the error message but cannot find much.
>>
>> Does anyone know if the way R calls unzip functions on Windows has
>> changed
>> and if this is permanent?
>> I am sorry if I miss something obvious, but any suggestions on how I can
>> fix the problem?
>> I want to keep using int.unzip and not the utils function unzip because
>> I
>> use its output afterwards in my script.
>
> Generally internal things that aren't documented as part of the API are
> subject to change without notice. Rather than relying on the way
> certain functions happen to work in certain versions, if you find that
> one of the documented functions doesn't do what you want, you should
> point out the problem with it and submit a patch.
>
> You can see how the unzip function in the utils package works by looking
> at the source, or just printing it in the console. It doesn't refer to
> int.unzip, but I wouldn't count on its current behaviour being
> "permanent": it's undocumented internal implementation, which you use
> at your own risk.
>
> Duncan Murdoch
>
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
[Rd] [PATCH] Typo in 'help' documentation
---
I think this should be "package is loaded" and not "library is
loaded". At least, I can't see how it can be correct the way it's
currently written.
-roger
src/library/utils/man/help.Rd |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git src/library/utils/man/help.Rd src/library/utils/man/help.Rd
index 5b0ed8e..783b0c2 100644
--- src/library/utils/man/help.Rd
+++ src/library/utils/man/help.Rd
@@ -135,7 +135,7 @@ type?topic
\note{
Unless \code{lib.loc} is specified explicitly, the loaded packages are
searched before those in the specified libraries. This ensures that
- if a library is loaded from a library not in the known library trees,
+ if a package is loaded from a library not in the known library trees,
then the help from the loaded library is used. If \code{lib.loc} is
specified explicitly, the loaded packages are \emph{not} searched.
--
1.5.5.1.99.gf0ec4
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
