If Martin's proposal for declaring non-S3 methods in NAMESPACE is feasible, it would be very helpful. The packages we support have multiple examples of unfortunately named functions non-S3 functions, so creating a route for migrating them into compliance would be great.
best, -skye On 06/12/2015 03:00 AM, r-package-devel-requ...@r-project.org wrote: > Message: 11 > Date: Fri, 12 Jun 2015 09:55:18 +0200 > From: Martin Maechler<maech...@stat.math.ethz.ch> > To: John Fox<j...@mcmaster.ca> > Cc: Michael Friendly<frien...@yorku.ca>, Sandy Weisberg > <sa...@umn.edu>, r-package-de...@r-project.org > Subject: Re: [R-pkg-devel] "apparent S3 methods" note in R CMD check > Message-ID:<21882.36966.429889.227...@stat.math.ethz.ch> > Content-Type: text/plain; charset="us-ascii" <snip> > that it would be desirable for the package author to > effectively declare the fact that such a function is not an S3 > method even though it "looks like it" at least if looked from far. > > So, ideally, you could have something like > > nonS3method("all.effects") > > somewhere in your package source ( in NAMESPACE or R/*.R ) > which would tell the package-checking code -- but*ALSO* all the other S3 > method code that all.effects should be treated as a regular R > function. ______________________________________________ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel