search for: exportclasspatterns

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]]

...lee( 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 lines. Chuck p.s. > sessionInfo() R version 2.12.0 (2010-10-15) Platform: i386-apple-darwin9.8.0/i386 (32-bit) locale: [1] C attac...

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'

Hi, Short answer: import 'as.matrix' and export your method(s) for it. From WRE: "All S4 classes to be used outside the package need to be listed in an exportClasses directive. Alternatively, they can be specified using exportClassPattern.(46) in the same style as for exportPattern. To export methods for generics from other packages an exportMethods directive can be used."

Georgi, Brilliant, thank you very much for the helpful reply and explanation! I added 'importFrom("Matrix","as.matrix")' to my NAMESPACE and all worked fine! As my 'as.matrix' method is used entirely internally to the 'testmat' function (and not "used outside the package"), I don't think I actually need to export it. In my case, testmat is

I've rolled up R-2.9.0.tar.gz a short while ago. This is a development release which contains a number of new features. Also, a number of mostly minor bugs have been fixed. See the full list of changes below. You can get it (later today) from http://cran.r-project.org/src/base/R-2/R-2.9.0.tar.gz or wait for it to be mirrored at a CRAN site nearer to you. In case of impatience, try

I've rolled up R-2.9.0.tar.gz a short while ago. This is a development release which contains a number of new features. Also, a number of mostly minor bugs have been fixed. See the full list of changes below. You can get it (later today) from http://cran.r-project.org/src/base/R-2/R-2.9.0.tar.gz or wait for it to be mirrored at a CRAN site nearer to you. In case of impatience, try

I've rolled up R-2.13.0.tar.gz a short while ago. This is a development release which contains a number of new features. Also, a number of mostly minor bugs have been fixed (but notice that serious build issues were fixed in 2.12.2). See the full list of changes below. You can get it from http://cran.r-project.org/src/base/R-2/R-2.13.0.tar.gz or wait for it to be mirrored at a CRAN site

I've rolled up R-2.13.0.tar.gz a short while ago. This is a development release which contains a number of new features. Also, a number of mostly minor bugs have been fixed (but notice that serious build issues were fixed in 2.12.2). See the full list of changes below. You can get it from http://cran.r-project.org/src/base/R-2/R-2.13.0.tar.gz or wait for it to be mirrored at a CRAN site