search for: loadpackagequietly

when using R CMD check mypkg I get the error message ... * checking R files for library.dynam ... OK * checking generic/method consistency ... WARNING Error in .loadPackageQuietly(package, lib.loc) : Error in parse(file, n, text, prompt) : syntax error on line 95 Execution halted * checking for assignment functions with final arg not named 'value' ... WARNING Error in .loadPackageQuietly(package, lib.loc) : Error in parse(file, n, text, prompt) : s...

I am trying to package some code that is a tweak to the survival package. When I asked earlier, the list consensus was that it would be best to do this as a separate package, dependent on survival. This is proving a bit tricky. I have some run-time and compile time concerns. Run-time, my R code needs R code from survival, and my C code needs C functions from survival. Will this all be

would it be possible to add an option to library that prevents messages except when there are errors? as we build Sweave documents illustrating package functionalities it is sometimes desirable to attach a package "behind the scenes". packages that have messages emitted in .First.lib (often describing version or developer) frustrate this particular desire. verbose=FALSE does not

Hi! Due to package maintenance I have removed some functions but forgot to update the coresponding Rd files. If R CMD check is checking for missing documentation entries why it does not check for documentation entries which tell the user about nonexisting funcitons? In my opinion checking for documentation entries that document non-existing functions is much more important than the other way