search for: __c__

...package.skeleton(name=name,environment=environment,path=path,namespace=namespace) }else{} ### Build up the list_S4 ### If list_S4 is empty : ### If code_files_S4 is not empty, the file in code_file_S4 are source. ### then list receive ls() after removing ".__C__" (either if code_files is empty or not) if (!is.character(code_files)){stop("'code_files S4' should be a character vector")}else{} use_code_files <- length(code_files) > 0 if (missing(list)){ ###############################################################...

...shey >> <kevinushey at gmail.com> wrote: >>> I have a small idea as to what's going on now; at least, >>> why exporting the class resolves this particular issue. >>> >>> Firstly, when an S4 class is not exported, the associated >>> '.__C__<class>' object is not made part of the package >>> environment. For example, I see: >>> >>>> getAnywhere(".__C__SubMatrix") A single object matching >>> '.__C__SubMatrix' was found It was found in the following >>> places...

Hi Martin, John, Thanks for the responses! I've tidied up some of the notes from this mailing list thread and posted them on the bug tracker. John, in this case, I think namespaces are relevant because for non-exported S4 classes, the class information is made available through the '.__C__<package>' symbol in the package's namespace, but not the package environment that gets attached to the search path. In this (rare, yet not impossible) sequence of events, it looks like R attempts to resolve the '.__C__<package>' symbol in the wrong environment, and so cl...

Dear All, I have a question of how to export S4 class specification to clusters/workers in parallel computing. The package I used is snowfall. The problem is reproducible as follows. Any hint is greatly appreciated. Edwin Sun === begin =========== library(snowfall) sfInit(parallel = TRUE, cpus = 2) setClass("catt", representation(aa = "numeric")) setClass("dogg",

Hi, (sorry for the wall of text; the issue here appears to be rather complicated) I'm seeing a somewhat strange case where checking whether an S4 object inherits from a parent class defined from another package with 'inherits' fails if that object is materialized through a call to 'load'. That's a mouthful, so I've put together a relatively small reproducible example

..., Kevin On Fri, Jul 29, 2016 at 11:37 AM, Kevin Ushey <kevinushey at gmail.com> wrote: > I have a small idea as to what's going on now; at least, why exporting > the class resolves this particular issue. > > Firstly, when an S4 class is not exported, the associated > '.__C__<class>' object is not made part of the package environment. > For example, I see: > > > getAnywhere(".__C__SubMatrix") > A single object matching '.__C__SubMatrix' was found > It was found in the following places > namespace:s4inher...

I have a small idea as to what's going on now; at least, why exporting the class resolves this particular issue. Firstly, when an S4 class is not exported, the associated '.__C__<class>' object is not made part of the package environment. For example, I see: > getAnywhere(".__C__SubMatrix") A single object matching '.__C__SubMatrix' was found It was found in the following places namespace:s4inherits with value < ....

...shey > <kevinushey at gmail.com> wrote: >> I have a small idea as to what's going on now; at least, >> why exporting the class resolves this particular issue. >> >> Firstly, when an S4 class is not exported, the associated >> '.__C__<class>' object is not made part of the package >> environment. For example, I see: >> >> > getAnywhere(".__C__SubMatrix") A single object matching >> '.__C__SubMatrix' was found It was found in the following >> place...