similar to: Namespace dependency not required

I have a problem with function 'inout()' in package 'splancs' on CRAN-R Version 1.2.3 under FreeBSD4.3-STABLE. The following script produces and draws points and a polygon-surrounded area. Repeating the same script many times shows, that points on the polygon-line often, but not always, are outside of the polygon-area. library(splancs) # dataset with polygon (convex

Dear all, It is my understanding that using 'importFrom' in the NAMESPACE of a package allows to avoid conflicts between different packages defining objects with identical names. However, I can still see conflicts while loading the package using 'library'. Here is a toy example, with a package 'foo' importing 'as.igraph' from the igraph package, and 'nj'

I'm still working to add namespace support to some of my packages. I've removed the 'Depends' line from the DESCRIPTION file, and created an appropriate NAMESPACE files. Strangely, whenever I use 'importFrom(package, function)' R CMD check generates "Namespace dependencies not required" warnings . Without the import statements, the warning does not occur, but

I am developing a package that imports some functions from another package. The imported package (qcc) does not have a namespace and this is causing problems with loading of my package, which has a namespace. Is there a workaround to allow loading the namespace-less package? I searched the archives and found a suggestion that the package should be included in the Depends list, but this has not

Hi, I am a bit unsure about using imports in packages and have a few questions. I'm sure the answer to some of these is 'it depends', but I'm interested in what others think and 'best practices' when this is the case. 1) If I use an import or importFrom declaration in a NAMESPACE, should I also qualify the package in calls to the imported function (e.g.

Dear All, I understand the R CMD checks with only the base package attached, everything else (including the other packages bundled with the base R) should be imported and most importantly declared in the Imports field from the DESCRIPTION file. However, I do use functions from other packages than base (utils, grDevices, stats, graphics), for which it is sufficient to declare importFrom() in the

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

Hi R users, I am developing two packages. Each package uses some functions from the other package. Now when I define these dependencies in the NAMESPACE file (via importFrom(XXXX,function1,....)), i get this error (when building one package): cyclic namespace dependency detected when loading 'XXXXXX', already loading ?YYYYYYY?, ?XXXXXXXXX? Is there any way to prevent this error?

On Mon, Mar 12, 2018 at 2:18 PM, Martin Maechler <maechler at stat.math.ethz.ch> wrote: > [...] > Is that so? Not according to my reading of the 'Writing R > Extensions' manual, nor according to what I have been doing in > all of my packages for ca. 2 years: > > The rule I have in my mind is > > 1) NAMESPACE Import(s|From) \ >

Hello, I try to set up namespaces for packages. It is fine for several of them, except one whose compilation fails (under Windows XP & R 2.0.0): ---------- Making package svViews ------------ adding build stamp to DESCRIPTION installing NAMESPACE file and metadata Error in parse(file, n, text, prompt) : syntax error on line 21 Execution halted make[2]: *** [nmspace] Error 1 make[1]: ***

I'd like to importFrom(parallel, mccollect, mcparallel) but on Windows these are not exported because this if(tools:::.OStype() == "unix") { export(mccollect, mcparallel, mc.reset.stream, mcaffinity) } appears at src/library/parallel/NAMESPACE:6 of svn r61857. So should I be doing if (tools:::.OStype() == "unix") { importFrom(parallel, mccollect, mcparallel) }

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

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)

I am cleaning up the rms package to not export functions not to be called directly by users. rms uses generic functions defined in other packages. For example there is a latex method in the Hmisc package, and rms has a latex method for objects of class "anova.rms" so there are anova.rms and latex.anova.rms functions in rms. I use:

Dear List, In one of my packages I have an S3 method for the plot3d generic function from package rgl. I am trying to streamline my Depends entries but don't know how to have plot3d(foo) in the examples section for the plot3d method in my package, without rgl being in Depends. Note that I importFrom(rgl, plotd3d) and register my S3 method via S3Method() in the NAMESPACE. If rgl is not in

A new function in my heplots package wants to use a non-exported utility function in the car package, df.terms, but this depends on other non-exported functions. From the Writing R extensions manual, I thought I could do this via (in my NAMESPACE) importFrom(car, car:::df.terms, car:::df.terms.default, car:::is.aliased) but I get: ** preparing package for lazy loading Error : objects

Hi, I am trying to build an R package so reading the manual on CRAN. I could figure out that using imports to load functions in your namespace would be the best bet to use in the Description file. After adding to the description file, I also added it to the namespace file. I added importFrom to the namespace file with the functions required. Now when I run R CMD check on my package, I get an

I'm trying to learn how to use namespaces, so I have created a small package with two functions. My NAMESPACE file is importFrom(survival, Surv) export(mlreg.fit, risksets) because 'mlreg.fit' uses 'Surv' from 'survival'. However I get * checking package dependencies ... WARNING Namespace dependencies not required: survival Why? (If I remove 'importFrom' I

Hi, Could someone point me to the relevant documentation that covers what should be in the DESCRIPTION file for packages that have functions imported via the NAMESPACE file? I have read the R Extensions manual, but I cannot find where it covers the DESCRIPTION file vis a vis importing from a namespace. An example: I have a package foo that uses two functions x and y from package bar. Both

Dear R-help, Can some one tell me if it's possible to have conditional importFrom() in the package NAMESPACE file? Basically I'd like to know if it's possible to make the NAMESPACE file compatible with R 1.9.0 and those 1.8.1 and earlier. The problem is that I want to import cmdscale(), which is in `mva' prior to 1.9.0 but in `stats' post 1.9.0. Any pointer much appreciated!