The MinGW-w64 project, whose toolchains we use for 64-bit Windows,
have made some changes to their conventions *and* removed all the
older binary builds from their site. The current toolchains are not
suitable for use with R 2.11.x, and I've re-packaged an older version
(which is) as
http://w
On Jul 23, 2010, at 2:46 PM, Paul Roebuck wrote:
> Is there a means of recovering the source from a package with LazyLoad =
> true? Package is Windows 2.9.1 pure R but have no access to original. In R
> directory, I see ,
> .rd[bx], .rd[bx]. Attempting this on OS X 10.6 with
> R-2.11.1 if it
On Jul 24, 2010, at 9:02 AM, John Hendrickx wrote:
> I'm trying to update my "perturb" package to get rid of some small warning
> messages. The examples in "perturb" use the "Duncan" dataset from the "car"
> package and I have "car" installed in R. But when I run "R CMD check", I get
> an
> e
Dear R-developers,
I am currently trying to develop a package with some customized
container classes and found an issue with the functions NROW and NCOL. I
guess that I can simply work around the problem by redefining these
functions in my own package (Yet, I do not know whether that will work
Is there a means of recovering the source from a package with LazyLoad = true?
Package is Windows 2.9.1 pure R but have no access to original. In R directory,
I see ,
.rd[bx], .rd[bx]. Attempting this on OS X 10.6 with R-2.11.1
if it matters.
Sent from my iPhone
___
I'm trying to update my "perturb" package to get rid of some small warning
messages. The examples in "perturb" use the "Duncan" dataset from the "car"
package and I have "car" installed in R. But when I run "R CMD check", I get an
error message
> require("car")
Loading required package: car
W
