Look at the definition of PrintValue:
void PrintValue(SEXP s)
{
PrintValueEnv(s, R_BaseEnv);
}
That's not going to find show from R_BaseEnv. We need to get it from the
methods namespace.
On Sat, 7 Apr 2007, Deepayan Sarkar wrote:
> Hi,
>
> I think this is a bug (even though I can't find
Hi,
Vince and I have noticed a problem with non-syntactic names in data
frames and some modeling code (but not all modeling code).
The following, while almost surely as documented could be a bit more
helpful:
m = matrix(rnorm(100), nc=10)
colnames(m) = paste(1:10, letters[1:10], sep="
Hi,
Any reason these should be different?
x=matrix(0, nr=0, nc=3)
colnames(x) = letters[1:3]
data.frame(x)
#[1] a b c
#<0 rows> (or 0-length row.names)
y=vector("list", length=3)
names(y) = letters[1:3]
data.frame(y)
#NULL data frame with 0 rows
both should have names (the second o
Robert Gentleman wrote:
> Hi,
>Vince and I have noticed a problem with non-syntactic names in data
> frames and some modeling code (but not all modeling code).
>
>The following, while almost surely as documented could be a bit more
> helpful:
>
> m = matrix(rnorm(100), nc=10)
> colnam
Deepayan,
you fail to load the methods package, so you cannot use S4. Eval
"library(methods)" first then everything is fine.
Cheers,
Simon
On Apr 7, 2007, at 7:33 PM, Deepayan Sarkar wrote:
> Hi,
>
> I think this is a bug (even though I can't find documentation
> explicitly saying that it sho
Deepayan,
don't mind my last mail - one shouldn't write e-mails before the
first cup of coffee in the morning ;).. "methods" used to be excluded
from the embedded startup (AFAIR), but that's no longer the case, so
it must be something else. Sorry for the noise (I'm off to get the
coffee :P
Dear package maintainers,
currently, 39 CRAN packages (not counting those on my
exclude-from-Windows lists) are not passing the checks under Windows for
R-2.5.0 alpha.
Additional 157 (!!!) packages are only passing with one or more WARNINGS.
Maintainers of failing packages will receive an autom
Simon,
There are a couple of subtle issues here. As I wrote, PrintValue
evaluates in the base environment, so sees only base functions. It is not
clear to me that is the right place (why the base environment and not the
base namespace, for example), and one might consider evaluating in
R_Glo
On 4/7/07, Prof Brian Ripley <[EMAIL PROTECTED]> wrote:
> The file is src/gnuwin32/fixed/bin/INSTALL.
>
> You do not want --vanilla: the point is to run R under normal conditions
> to pick up the value it uses. There is a workaround on the Unix side, nd
> I will add a similar one to the Windows c
Indeed, you run into the same problem when trying to use PrintValue in
a package (say, for debugging purposes). I just have an implementation
that uses GlobalEnv instead of BaseEnv though I'm not sure that it's
necessarily the correct choice (though it has yet to do something I
don't want).
On 4/8
10 matches
Mail list logo
