I am not sure if this is the right place for that kind of questions, but I wondered that the recommended package survival did not pass R's check procedure without warnings: 1) unbalanced braces: * Rd files with unbalanced braces: * man/Surv.Rd * man/cluster.Rd * man/cox.zph.Rd * man/coxph.Rd * man/coxph.detail.Rd * man/date.ddmmmyy.Rd * man/lines.survfit.Rd * man/plot.cox.zph.Rd * man/predict.survreg.Rd * man/pyears.Rd * man/residuals.coxph.Rd * man/stanford2.Rd * man/strata.Rd * man/summary.survfit.Rd * man/survdiff.Rd * man/survexp.Rd * man/survfit.Rd * man/survreg.control.Rd * man/survsum.Rd * man/untangle.specials.Rd 2) missing docs: * checking for undocumented objects ... WARNING [1] "[.Surv" "[.coxph.penalty" [3] "[.ratetable" "[.ratetable2" [5] "[.survfit" "[.tcut" [7] "[.terms" "anova.survreg" [9] "anova.survreglist" "as.character.Surv" [11] "as.data.frame.Surv" "as.data.frame.difftime" [13] "as.matrix.ratetable" "coxpenal.fit" [15] "format.Surv" "is.category" [17] "is.na.Surv" "is.na.coxph.penalty" [19] "is.na.ratetable" "is.na.ratetable2" [21] "labels.survreg" "match.ratetable" [23] "model.frame.coxph" "model.frame.survreg" [25] "model.newframe" "print.coxph.penal" [27] "print.ratetable" "print.summary.survreg" [29] "print.survdiff" "print.survexp" [31] "print.survreg.penal" "residuals.survreg.penal" [33] "summary.coxph.penal" "summary.ratetable" [35] "survexp.cfit" "survpenal.fit" [37] "survreg.fit" "tcut" 3) non-matching docs: * checking for code/documentation mismatches ... WARNING $as.date $as.date$code [1] "x" "order" "..." $as.date$docs [1] "x" If I did not miss something, these are bugs, but not of R, but of a contributed package. What is the right place for reporting such bugs? Kind regards, Thomas. -- Thomas Hoffmann Telephone: 49-351-4598831 thoffman at zappa.sax.de Dresden, Germany ..sig under construction ... -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-help mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html Send "info", "help", or "[un]subscribe" (in the "body", not the subject !) To: r-help-request at stat.math.ethz.ch _._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._
On Mon, 12 Nov 2001, Thomas Hoffmann wrote:> I am not sure if this is the right place for that kind of questions, but > I wondered > that the recommended package survival did not pass R's check procedure > without > warnings:Well, that's the check for the next version of R applied to code prepared for the last version of R. You could try the checks on R 1.3.0 say .... Having these tools (principally thanks to Kurt) has enabled us to catch literally hundreds of small problems and a few bigger ones. [...]> If I did not miss something, these are bugs, but not of R, but of a > contributed > package. What is the right place for reporting such bugs?R-bugs, Cc:ed the package maintainer, I think. R-bugs has a section called `Add-ons' for contributed code. Do remember that survival is a port, and porters do find it hard to document other people's code. Certainly some of the packages I have ported have undocumented functions solely because I do not know what they are supposed to do. -- Brian D. Ripley, ripley at stats.ox.ac.uk Professor of Applied Statistics, http://www.stats.ox.ac.uk/~ripley/ University of Oxford, Tel: +44 1865 272861 (self) 1 South Parks Road, +44 1865 272860 (secr) Oxford OX1 3TG, UK Fax: +44 1865 272595 -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-help mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html Send "info", "help", or "[un]subscribe" (in the "body", not the subject !) To: r-help-request at stat.math.ethz.ch _._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._
On Mon, 12 Nov 2001, Thomas Hoffmann wrote:> I am not sure if this is the right place for that kind of questions, but > I wondered > that the recommended package survival did not pass R's check procedure > without > warnings:In general reports on packages should go to the maintainer. In fact, I know about these, and some of them have been fixed. For CRAN packages you can usually rely on the CRAN maintainers to have told the package maintainer about this sort of thing (and the package maintainer probably already knew even before that). -thomas -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-help mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html Send "info", "help", or "[un]subscribe" (in the "body", not the subject !) To: r-help-request at stat.math.ethz.ch _._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._