search for: exportpatterns

Hello, I wrote a package, which in the NAMESPACE file exports functions like this: exportPattern("^\\rh") On R-2.8 (Linux, 64), upon loading the package I have the rh functions present. On R-2.10, Mac OS X, (32 bit), it builds, loads, but the functions are not loaded, i.e the only function is rhyper (which is not from my package). Is there something wrong with my package setup?

Dear List: Sorry for posting maybe a trivial question, but I have a basic understanding problem. If I have say pack1 and pack2, two R packages, and pack2 depends on and imports pack1 fully (as in the code below), is there a way to make all the functionality of pack1 available for the global and other environments (not only for the functions called from withing pack2) by loading pack2 only? I

The Rcpp package and some related packages such as RcppArmadillo make use of (local) wrappers around the utils::package.skeleton() function for creating (basic yet functional) packages using Rcpp or RcppArmadillo. RStudio also exposes this under the graphical menu as a nice way to construct a package. But it seems that something changed quite recently in R. I looked into this a little yesterday

It would be nice to have a more convenient means of exporting multiple classes from a package namespace. Why not have something like exportClassPattern() that worked like exportPattern() except for classes? Thanks, Michael [[alternative HTML version deleted]]

Hello to the list Some days ago, I placed a question on this maling-list and received an answer from Martin that I tried to follow. Unfortunately, I am still puzzled by the next step. I spent the whole Week-end in gathering information from the net. Some of them are almost contridtcory and I lack a good document to help me. So my first question would beL Is there a convenient document which

Hello all. I'm building a package where I want to include a function from two different packages. In particular, I want to include mvrnorm and hyperg_2F1 from MASS and gsl, respectively (but the specific functions do not matter). With what I've tried after reading the "Specifying imports and exports" section from the "Writing R Extensions" manual, I get an error:

No. I fixed that, the NAMESPACE file now contains: S3method("[[<-", mylist) S3method("$<-", mylist) It still does not work. I also created a print method (print.mylist) which did work out of the box, regardless of being in the NAMESPACE file or not. Could it be somehow in here (also in my NAMESPACE file): exportPattern("^[[:alpha:]]+") Or could it be that

Hi, In R version 2.4.0 beta (2006-09-24 r39502) I'm seeing the following behavior with the tcltk package: > library("tcltk") Loading Tcl/Tk interface ... done > tkfile.dir() Error: 'tkfile.dir' is defunct. Use 'tclfile.dir' instead. See help("Defunct") > tclfile.dir Error: object "tclfile.dir" not found ## But the function is in the

I have been struggling all day to import a particular function/method combination (ranef(), which extracts the random effects from a mixed model fit) from the nlme package into another package ... so far without success. The NAMESPACE for nlme contains the following lines: export(..., ranef, ...) S3method(ranef, lme) ranef is defined as a standard S3 generic, function (object, ...)

Buenos días, Me han surgido unas cuantas dudas sobre la creación de librerías, las cuales las enumero a continuación: - NAMESPACE: ¿si deseo cargar un paquete o librería como he de hacerlo? ¿he de poner ( exportPattern("^[[:alpha:]]+") ) y entre las comillas la ubicación del paquete? -Queremos grabar una función habla de hacerlo con dump, y la duda es que como entradas solo tiene el

> ... reports that the fortran names of all the registered fortran functions are ?undocumented objects?... Those symbols should not be exported. In quantreg v5.33, NAMESPACE has 'exportPattern(".")'. Maybe it is a good time to remove that and export explicitly the symbols that are meant for export. Georgi Boshnakov ------------------------------ Message: 6 Date: Fri, 28

...l )\nexport( outDS )\n",file="NAMESPACE") > readLines("NAMESPACE") [1] "blah( nada )" "blee( nil )" "export( outDS )" > parseNamespaceFile("",".") # now parse it $imports list() $exports [1] "outDS" $exportPatterns character(0) $importClasses list() $importMethods list() $exportClasses character(0) $exportMethods character(0) $exportClassPatterns character(0) $dynlibs character(0) $nativeRoutines list() $S3methods [,1] [,2] [,3] > So, it picked up 'export' and ignored the other two...

On 06/06/2020 3:06 p.m., Dirk Eddelbuettel wrote: > > The Rcpp package and some related packages such as RcppArmadillo make use of > (local) wrappers around the utils::package.skeleton() function for creating > (basic yet functional) packages using Rcpp or RcppArmadillo. RStudio also > exposes this under the graphical menu as a nice way to construct a package. > > But it

Hello, (Dear Richard, I hope you don't mind being Cc:'d on this thread in R-devel. This is one of the ways we can prevent similar problems from happening in the future.) Sometimes, package authors who use both exportPattern('.') and utils::globalVariables(...) get confusing WARNINGs about undocumented exports: https://stat.ethz.ch/pipermail/r-package-devel/2024q1/010531.html I

the NEWS file for R-devel says * Even data-only packages without *R* code need a namespace and so may need to be installed under *R* 2.14.0 or later. but what should this contain? Can it simply be an empty NAMESPACE file? I assume that data does not have to be exported. -Michael -- Michael Friendly Email: friendly AT yorku DOT ca Professor, Psychology Dept. York University

Dear all, I get a bug in the examples of my AFLP package on R-forge (https://r-forge.r-project.org/R/?group_id=1027) but only on the Linux version. The windows version compiles. The Mac version skips the examples and compiles. The strange thing is that the packages compiles on my Ubuntu 10.10 machine with R 2.15.0. Therefore I can't reproduce the error. I have traced the problem at

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'

Dear all, I'm writing a package and I would like to reuse the residuals() function. When I use a function which calls the redefined residuals (for my custom class) I get an error (see below). It looks like the wrong method is used. The strange this is, that when it execute the code manually it get no error. Any suggestions? Best regards, Thierry The entire source code is at

To all. I need your help. The big question is: How do I make an R library with Fortran 95 files? You may assume that I am a pretty decent programmer in both R and Fortran. I lay out a scenario and need your help! I know how to make an ordinary R package and have dabbled with R + Fortran 95 *.dll linking. I do not have a great handle on the whole Makevars file and whatever else I might need

Hi all. I'm for the first time trying to make a library in R 2.8.1 on Ubuntu Linux. The library is very simple, R functions just need to share a variable (that is defined in the R code) and maybe functions and export functions for the user to .GlobalEnv. This variable should only be directly accessible from the global workspace (without change of environment) via a hereto dedicated function.