search for: importmethode

parseNamespaceFile() doesn't seem to detect misspelled directives. Looking at its code I see switch(as.character(e[[1L]]), <lots of args omitted here>, stop(gettextf("unknown namespace directive: %s", deparse(e)), call. = FALSE, domain = NA)) but this doesn't seem to function as I expect, viz. to stop with an error if I type a wrong directive.

...version %s cannot be unloaded:\n %s Paket %s Version %s kann nicht entladen werden\n%s% po/R-de.po:1271 too few entries No generic function %s found corresponding to requested imported methods from package %s when loading %s (malformed exports?) Keine generische Funktion, die mit der angeforderten Importmethode f<U+00FC>r\n%s aus Paket %s korrespondiert, gefunden (Fehler in Exports?) not installing 2. on all packages for .da (easy to fix): po/R-da.po:2: warning: header field 'Language-Team' still has the initial default value ## An easy solution to update/test (R and..) translations #...

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

This is an enquiry not so much about what the code for loadNamespace does, but rather about the intent and design of loadNamespace, and how it interacts with the `::` function, which seems to me to follow a slightly different philosophy. It is not an urgent question - the issue that started me wondering has been resolved another way - but I would like to complete my understanding of this aspect