search for: checkdocstyl

...ot;package:base" > library(Tools) Attaching package 'Tools': The following object(s) are masked from package:tools : .checkDemoIndex .checkVignetteIndex .installMD5sums .installPackageDescription .installPackageIndices buildVignettes checkAssignFuns checkDocArgs checkDocStyle checkFF checkMD5sums checkMethods checkTnF checkVignettes codoc md5sum pkgVignettes print.checkAssignFuns print.checkDemoIndex print.checkDocArgs print.checkDocStyle print.checkFF print.checkMethods print.checkTnF print.checkVignetteIndex print.checkVignettes print.codoc print.undoc Rdindex Rtangl...

...[6]: Leaving directory `/data/prog/R-2.9.1/src/library/tools/src' make[5]: Leaving directory `/data/prog/R-2.9.1/src/library/tools/src' make[4]: Leaving directory `/data/prog/R-2.9.1/src/library/tools' Error in namespaceExport(ns, exports) :   exportations non définies : checkDocFiles, checkDocStyle, checkFF, checkReplaceFuns, checkS3methods, checkTnF, codoc, codocClasses, codocData, undoc Calls: ::: ... tryCatch -> tryCatchList -> tryCatchOne -> <Anonymous> In addition: Warning message: les méthodes S3 ‘print.checkDocFiles’, ‘print.checkDocStyle’, ‘print.checkFF’, ‘print.check...

...n halted Functions with \usage entries need to have the appropriate \alias entries, and all their arguments documented. The \usage entries must correspond to syntactically valid R code. See the chapter 'Writing R documentation files' in manual 'Writing R Extensions'. Error in tools::checkDocStyle(package = "penalized") : directory 'M:/R/packages/penalized.Rcheck/penalized' does not contain Rd sources Execution halted The \usage entries for S3 methods should use the \method markup and not their full name. See the chapter 'Writing R documentation files' in manual...

...it now acts consistently with the other verbatim-like environments (it was never 'verbatim' despite the documentation). \code{\.} is now rendered as '\.' in all formats, as documented (it was not the case for latex conversion). codoc() (and checkDocStyle() and checkDocUsage()) now apply the same transformations to \usage as Rd conversion does, so {, % and \\ in strings in usages will now be related correctly to the help files. o rbind() failed if the only data frame had 0 rows. (PR#9657) o <a data.frame>...

...it now acts consistently with the other verbatim-like environments (it was never 'verbatim' despite the documentation). \code{\.} is now rendered as '\.' in all formats, as documented (it was not the case for latex conversion). codoc() (and checkDocStyle() and checkDocUsage()) now apply the same transformations to \usage as Rd conversion does, so {, % and \\ in strings in usages will now be related correctly to the help files. o rbind() failed if the only data frame had 0 rows. (PR#9657) o <a data.frame>...

...ow used for analyzing the markup in the \usage sections. Hence in particular, replacement functions or S3 replacement methods are no longer ignored. - checkDocFiles() now also determines 'over-documented' arguments which are given in the \arguments section but not in \usage. - checkDocStyle() and checkS3Methods() now know about internal S3 generics and S3 group generics. - S4 classes and methods are included in the QC tests. Warnings will be issued from undoc() for classes and methods defined but not documented. Default methods automatically generated from nongeneric...

...ow used for analyzing the markup in the \usage sections. Hence in particular, replacement functions or S3 replacement methods are no longer ignored. - checkDocFiles() now also determines 'over-documented' arguments which are given in the \arguments section but not in \usage. - checkDocStyle() and checkS3Methods() now know about internal S3 generics and S3 group generics. - S4 classes and methods are included in the QC tests. Warnings will be issued from undoc() for classes and methods defined but not documented. Default methods automatically generated from nongeneric...