search for: exportclasspattern

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 atta...

...o Author: John Doe Maintainer: John Doe <jdoe at nowhere.org> Imports: igraph, ape Description: just a test. License: GPL (>=2) LazyLoad: yes ---------------------- And the following NAMESPACE: ---------------------- ## Export all names exportPattern(".") ## Export all classes exportClassPattern(".") ## Import all packages listed as Imports or Depends importFrom(igraph, as.igraph) importFrom(ape, nj) ---------------------- The check (R 3.0.1) passes without warnings, but then when loading the package: > library(foo) Warning messages: 1: replacing previous import ?as.igraph?...

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." Details: the precise details depend on what exactly is in your NAMESPACE file. The curious difference you observe is due to the fact that as.matrix is defi...

...trading.net> Subject: RE: R-devel Digest, Vol 167, Issue 25 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." Details: the precise details depend on what exactly is in your NAMESPACE file. The curious difference you observe is due to the fact that as.matrix is defi...

...s of list arguments, not just vectors and factors. o plot.ts(plot.type="multiple") now makes use of *.lab and *.axis graphical parameters (wish of PR#13134 and 13135). o Classes can be exported from a name space using the NAMESPACE file directive 'exportClassPattern' which has the same syntax as 'exportPattern'. o strftime() now converts its first argument with as.POSIXlt() and so is no longer an alias for format.POSIXLt. o body<-() now treats list values consistently with other types: they no longer need to...

...s of list arguments, not just vectors and factors. o plot.ts(plot.type="multiple") now makes use of *.lab and *.axis graphical parameters (wish of PR#13134 and 13135). o Classes can be exported from a name space using the NAMESPACE file directive 'exportClassPattern' which has the same syntax as 'exportPattern'. o strftime() now converts its first argument with as.POSIXlt() and so is no longer an alias for format.POSIXLt. o body<-() now treats list values consistently with other types: they no longer need to...

...e and recommended packages. ? Providing an exportPattern directive in a NAMESPACE file now causes classes to be exported according to the same pattern, for example the default from package.skeleton() to specify all names starting with a letter. An explicit directive to exportClassPattern will still over-ride. ? There is an additional marked encoding "bytes" for character strings. This is intended to be used for non-ASCII strings which should be treated as a set of bytes, and never re-encoded as if they were in the encoding of the currrent locale: u...

...e and recommended packages. ? Providing an exportPattern directive in a NAMESPACE file now causes classes to be exported according to the same pattern, for example the default from package.skeleton() to specify all names starting with a letter. An explicit directive to exportClassPattern will still over-ride. ? There is an additional marked encoding "bytes" for character strings. This is intended to be used for non-ASCII strings which should be treated as a set of bytes, and never re-encoded as if they were in the encoding of the currrent locale: u...