McGehee, Robert wrote:
The bug might be here:
is.null(expression())
[1] TRUE
But
is.null(expression(NULL))
[1] FALSE
So it might look to the methods package like you're passing in a NULL
value for @bar. I might argue that expression() should not be NULL (and
only NULL is NULL) as I
Something in new() or validObject() in the methods package is messing
up. This happens in both 2.1.0 and R-devel in Windows.
I'd like to have an empty expression for a slot in a class. An empty
expression is an expression:
is.expression(expression())
[1] TRUE
is(expression(),
[EMAIL PROTECTED] writes:
Is it doing an extra eval or something? It looks like it:
x - expression()
x
expression()
eval(x)
NULL
x - quote(expression())
x
expression()
eval(x)
expression()
eval(eval(x))
NULL
You do realize that the two expression() results are
The bug might be here:
is.null(expression())
[1] TRUE
But
is.null(expression(NULL))
[1] FALSE
So it might look to the methods package like you're passing in a NULL
value for @bar. I might argue that expression() should not be NULL (and
only NULL is NULL) as I have had similar trouble trying to
