search for: nons3method

And my non-cross-posted cross-posting: "Dear Martin, Thank you for addressing this issue. Introducing a nonS3method() directive in NAMESPACE seems a reasonable solution. It could replace export() for functions with "."s in their names. Best, John" On Fri, 12 Jun 2015 10:12:07 +0200 Martin Maechler <maechler at stat.math.ethz.ch> wrote: > This is a topic ' "apparent S3 methods...

...R core > member .. 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. > I would very much lik...

...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. >...

...ot; <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.

...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 >>>&g...

...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 treat...

...d 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. &g...

...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 t...

...;>>>> 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...

...;>>>>> 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 >>>>&...

...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...