search for: _namespace_

The Writing R Extensions manual instructs developers who use S4 classes and methods in a package with a name space to: There needs to be an .onLoad action to ensure that the methods package is loaded and attached: .onLoad <- function(lib, pkg) require(methods) I'm wondering if listing methods in the Depends field of the package's DESCRIPTION file is sufficient.

...`validObject` -> `getClassDef` -> `.requirePackage` set of calls. When `.requirePackage` does not find our package already loaded, it loads, attaches it, and returns the _package_ environment. This is different to what happens when the package namespace is already loaded, in which case the _namespace_ environment is returned. The problem with the _package_ environment is that any unexported class definitions will not be found there. This is why `validObject` fails the first time, but works the second. The first time the package is loaded and `getClassDef` is given the package env to look in,...

http://25thandclement.com/~william/openssh-4.3p2-streamlocal-20060421.patch The above URL is a complete patch to OpenSSH 4.3p2 to implement unix domain socket forwarding (this supercedes a canceled message I sent last night w/ an inline attachment). Basically, for forward and reverse forwardings anywhere you previously put a port number you can now put a path. The socket path should go between

...ed [3]: findClass('CsparseMatrix', loadNamespace('SeuratObject')) # [[1]] # <environment: 0x560676e863c8> # attr(,"name") # [1] "imports:SeuratObject" In SeuratObject_4.1.3, the class was not imported, so methods:::.findOrCopyClass() used the SeuratObject _namespace_ as the environment to assign the class definition in. Are there ways to prevent this problem (by importing more classes?) or at least warn about it at package check time? How prevalent is class copying on CRAN? Out of 358 packages installed on my machine, many no doubt outdated, only six copy fore...

...ix', loadNamespace('SeuratObject')) > # [[1]] > # <environment: 0x560676e863c8> > # attr(,"name") > # [1] "imports:SeuratObject" > > In SeuratObject_4.1.3, the class was not imported, so > methods:::.findOrCopyClass() used the SeuratObject _namespace_ as the > environment to assign the class definition in. > > Are there ways to prevent this problem (by importing more classes?) or > at least warn about it at package check time? How prevalent is class > copying on CRAN? Out of 358 packages installed on my machine, many no > doub...