search for: importmethods

...t;) > 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 lines. Chuck p.s. > sessionInfo() R version 2...

Dear R users/devs, TL;TR This is a translations status for R. Since I've revisited my own work in a github repo, I think some notes could be useful to other maintainers. ## Status The supported languages for "base": da, de, en, en_GB, es, fa, fr, it, ja, ko, nn, pl, pt_BR, ru, tr, zh_CN, zh_TW. Any single file is quite close to be completed (# of translated labels), but some

Hi, I'm hoping to get some clarification of the intent of some of directives used in NAMESPACE files. 1. Is import(somePkg) also intended to import all classes and methods that are exported via exportClasses and exportMethods in somePkg? I think import pulls in classes and methods, but it isn't clear from the docs whether this is as intended. 2. What is exportMethods intended

...The checking occurs inside 3 loops, which all use an appropriate entry from vI as the versionCheck argument in a recursive call to loadNamespace, viz. for (i in nsInfo$imports) { ...etc... } for (imp in nsInfo$importClasses) ...etc... for (imp in nsInfo$importMethods) ...etc... AN ASIDE ABOUT loadNamespace AND Depends: ===================================== As an aside it appears that any version dependencies specified in the Depends field are overlooked - I suspect that loadNamespace might be more complete if there were something like vD <- pkgI...