Winston,
Sounds like you might be better of constructing and evaluating an
expression:
> test = setRefClass("test", methods = list(m1 = function() "hi", m2 =
function() "lo", byname = function(nm) {
+ expr = substitute(.self$xXx(), list(xXx = nm))
+ eval(expr)
+ }))
> thing = test$new
On Wed, Oct 16, 2013 at 3:41 PM, Gabriel Becker wrote:
> Winston,
>
> (back on list since I found some official info)
>
> Looks like the behavior you are seeing is "documented-ish"
>
> Only methods actually used will be included in the environment corresponding
> to an individual object. To decla
Winston,
(back on list since I found some official info)
Looks like the behavior you are seeing is "documented-ish"
Only methods actually used will be included in the environment
corresponding to an individual object. To declare that a method requires a
particular other method, the first method
When a reference class method is accessed with .self$x, it has
different behavior from .self[['x']]. The former copies the function
to the object's environment (with some attributes attached), and the
latter just return NULL (unless it has already been accessed once with
.self$x). Is this how it's
On Oct 16, 2013, at 02:41 , Nigel Delaney wrote:
> Okay, so I am guessing everyone had the same response I initially did when
> hearing that this RNG might not be so hot*... as an alternate question, if
> I submitted a patch to replace the current RNG with the twister, would it be
> accepted?
On 15/10/2013 14:00, Rosenberger George wrote:
Dear R Developers
I'm using the great randomForest package (4.6-7) for many projects and recently
stumbled upon a problem when I wrote unit tests for one of my projects:
On Windows, there are small numeric deviations when using the 32- / 64-bit
v
Dear R Developers
I'm using the great randomForest package (4.6-7) for many projects and recently
stumbled upon a problem when I wrote unit tests for one of my projects:
On Windows, there are small numeric deviations when using the 32- / 64-bit
version of R, which doesn't seem to be a problem o
Paul,
For our HPC cluster we have ran into this issue in the past. What we use is
modules[1]. We instructor our users to run a command, like
modules load R/2.15.2
This will load up the environment path in which R/2.15.2 lives. If they want
to switch or use R/3.0.1 they simply run
module u
