similar to: data() documentation ambiguous about loaded versus attached packages?

PkgA wishes to write a method for 'unique' on S4 class 'A'. ?Methods indicates that one should setGeneric("unique") setClass("A") unique.A <- function(x, incomparables=FALSE, ...) {} setMethod(unique, "A", unique.A) Both S3 and S4 methods need to be exported in the NAMESPACE import(methods) S3method(unique, A)

Hi, I started this post on bioc-devel but this seems to be more general: https://stat.ethz.ch/pipermail/bioc-devel/2013-May/004311.html See reproducible example from Martin below. Thank you. Renaud ---------- Forwarded message ---------- From: Martin Morgan <mtmorgan at fhcrc.org> Date: 7 May 2013 19:55 Subject: Re: [Bioc-devel] ExpressionSet and LumiBatch: inheritance problem in S4

In > R.version.string [1] "R Under development (unstable) (2011-12-15 r57901)" section 1.6.6 of 'Writing R Extensions' says Note that exporting methods on a generic in the namespace will also export the generic, and exporting a generic in the namespace will also export its methods. and Note that importMethodsFrom will also import any generics defined in

pkgA's NAMESPACE has importFrom(graphics, plot) exportClasses("A") exportMethods("plot") R/foo.R has setClass("A") setMethod("plot", "A", function(x, y, ...) {}) During R CMD INSTALL pkgA_1.0.tar.gz we are told ** preparing package for lazy loading Creating a generic function for 'plot' from package

In > R.version.string [1] "R Under development (unstable) (2011-12-15 r57901)" PkgA promotes 'unique' to a generic and exports that DESCRIPTION: Imports: methods R/f.R: setGeneric("unique") NAMESPACE: export(unique) and PkgB creates and exports a method on unique DESCRIPTION Imports: methods, PkgA R/f.R: setClass("B",

>>>>> Martin Morgan <mtmorgan at fredhutch.org> >>>>> on Mon, 11 May 2015 10:18:07 -0700 writes: > On 05/10/2015 08:19 AM, Martin Morgan wrote: >> Loading an S4 object from a file without first loading the library sometimes (?, >> the example below and actual example involves a virtual base class and the show >> generic)

Loading an S4 object from a file without first loading the library sometimes (?, the example below and actual example involves a virtual base class and the show generic) leads to incorrect dispatch (to the base class method). The attached package reproduces the problem. It has setClass("A") setClass("B", contains="A") setMethod("show", "A",

On 05/10/2015 08:19 AM, Martin Morgan wrote: > Loading an S4 object from a file without first loading the library sometimes (?, > the example below and actual example involves a virtual base class and the show > generic) leads to incorrect dispatch (to the base class method). > > The attached package reproduces the problem. It has The package was attached but stripped; a version is

PkgA has a single R/binding.R file containing .A <- setRefClass("A", methods=list(initialize=function(...) {})) .onLoad <- function(...) .A() A NAMESPACE with import(methods) exportClasses("A") and DESCRIPTION Package: PkgA Type: Package Title: Documenting reference classes Version: 0.0.1 Date: 2012-08-05 Author: Martin

Dear list, It seems that a package (pkgB) using another package (pkgA) with S4 generics formed by taking existing functions (for example 'plot') must not import the existing functions ('plot') in its namespace to avoid the warning "replacing previous import: plot". Suppose we use the simple 'import' directive in the name space of pkgB. pkgA and pkgB files would

Hi, not sure this is a bug or just an unavoidable undesirable side-effect -- or just me that does not do the right thing. Consider the code and output below. It creates 2 packages: * pkgA * pkgB that creates a method for a generic defined in pkgA Changes in a method for the generic in pkgA (after re-installing pkgA) are not reflected in pkgB, unless pkgB is re-installed against the new

I was wondering: are the downstream dependencies of a package rebuilt when a package is updated on CRAN? (I'm referring to the binary packages, of course.) The reason I ask is because there are cases where this can cause problems. Suppose that when pkgB is built, it calls pkgA::makeClosure(), which returns a closure that refers to a function in pkgA. Suppose this code is in pkgA 1.0:

Hi, This strange warning happen sometimes when running 'R CMD check': * checking whether the package can be loaded with stated dependencies ... WARNING Error : .onLoad failed in loadNamespace() for ?pkgB?, details: call: length(new("A")) error: could not find function "loadMethod" Error: package/namespace load failed for ?pkgB? Execution halted

Hi, SETUP: Consider three packages PkgA, PkgB and PkgC. PkgA defines a generic function foo() and exports it; export(foo) PkgB imports PkgA::foo() and re-exports it; importFrom(PkgA, foo) export(foo) PkgC imports everything from PkgA and PkgB: imports(PkgA, PkgB) PROBLEM: Loading or attaching the namespace of PkgC will generate a warning: replacing previous import by

Hi, I'd like to list all package PkgA functions that another package PkgB use via Depends or Imports (ignoring Suggests for simplicity). As long as PkgB uses importFrom("PkgA", ...) it's just a matter of parsing the NAMESPACE file or inspecting asNamespace("PkgB")$.__NAMESPACE__.$imports. However, what can be done in case PkgB uses import("PkgA")? Is there

In this post https://stat.ethz.ch/pipermail/bioc-devel/2013-March/004152.html a package author reports that S4 dispatch fails. I can reproduce this with a PkgA (attached; 'intervals' is a relatively light-weight CRAN package) that has DESCRIPTION with Depends: intervals Imports: graphics NAMESPACE: importFrom(graphics, "plot") export("plot")

Hi Sebastian, On Thursday, 23 August 2018 16:45:27 CEST Sebastian Meyer wrote: > The `-l` option for some `zypper` subcommands is short for > `--auto-agree-with-licenses` and not available on the `zypper rm` command. > No problem with the patch, just one question: can it happen that zypper may decide to install packages when removing others, e.g. to keep some other

Suppose I have a function funcA() in package pkgA that requires function funcB() from another package pkgB under certain circumstances. Those circumstances are rare though, so I put package pkgB under 'Suggests', and use this in funcA() when those circumstances do arise: if (require("pkgB", quietly=TRUE)) { pkgB::funcB(...) } else { stop("Please install package

I am trying to build the latest version of R (3.6.2) on a CentOS system running 7.7.1908. I have been able to build previous versions of R up to and including 3.5.3 successfully. Starting with 3.6.0 the "make check" step fails with errors relating to "pdflatex" being missing. So, I installed texlive-latex (and the 100 other rpm dependencies) then tried rebuilding R.

Dear list, // IN SHORT // What are possible workarounds to "consolidate" documentation for S4 methods that are scattered across different packages (generic and some custom methods in one package, additional custom methods in another package) in a *single* Rd help file while using package 'roxygen2' to generate the actual Rd files? // ADDITIONAL INFORMATION // First of, here