On 09/05/2023 5:05 p.m., Simon Urbanek wrote:
Duncan,
you're right that any functions in the call environment are always treated as
methods (even before consulting method registrations). That is a special case -
I presume for compatibility with the world before namespaces so that, e.g., you
d
Duncan,
you're right that any functions in the call environment are always treated as
methods (even before consulting method registrations). That is a special case -
I presume for compatibility with the world before namespaces so that, e.g., you
don't have to register methods in the global envi
Dear Ulrike
Even though it will undobtedly be a lot of work to rename levels.no I
cannot help feeling that by fighting against the system you may be
storing up trouble for yourself in future when some upgrade breaks your
current solution and you have to make yet more changes.
Michael
On 09/
Am 09.05.2023 um 01:23 schrieb Duncan Murdoch:
On 08/05/2023 6:58 p.m., Simon Urbanek wrote:
On 8/05/2023, at 11:58 PM, Duncan Murdoch
wrote:
There really isn't such a thing as "a function that looks like an S3
method, but isn't". If it looks like an S3 method, then in the
proper circum
If anyone wants to try my demo, they can install the test package using
remotes::install_github("dmurdoch/testpkg")
and see the demonstration by running
library(testpkg)
example(f)
Duncan Murdoch
On 08/05/2023 7:23 p.m., Duncan Murdoch wrote:
On 08/05/2023 6:58 p.m., Simon Urbanek wrot
On 08/05/2023 6:58 p.m., Simon Urbanek wrote:
On 8/05/2023, at 11:58 PM, Duncan Murdoch wrote:
There really isn't such a thing as "a function that looks like an S3 method, but
isn't". If it looks like an S3 method, then in the proper circumstances, it will be
called as one.
I disagree
> On 8/05/2023, at 11:58 PM, Duncan Murdoch wrote:
>
> There really isn't such a thing as "a function that looks like an S3 method,
> but isn't". If it looks like an S3 method, then in the proper circumstances,
> it will be called as one.
>
I disagree - that was the case in old versions,
On 08/05/2023 12:10 p.m., Ulrike Groemping wrote:
Am 08.05.2023 um 15:48 schrieb Duncan Murdoch:
On 08/05/2023 8:28 a.m., Ulrike Groemping wrote:
Thanks, Duncan. I appreciate the view that levels.no acts as an S3
method for the generic levels, if an object of class "no" is handed to
it. However
Am 08.05.2023 um 15:48 schrieb Duncan Murdoch:
On 08/05/2023 8:28 a.m., Ulrike Groemping wrote:
Thanks, Duncan. I appreciate the view that levels.no acts as an S3
method for the generic levels, if an object of class "no" is handed to
it. However, as the function is not intended as an S3 method,
On 08/05/2023 8:28 a.m., Ulrike Groemping wrote:
Thanks, Duncan. I appreciate the view that levels.no acts as an S3
method for the generic levels, if an object of class "no" is handed to
it. However, as the function is not intended as an S3 method, it does
not make sense to document it as such. A
I certainly could, but I'm using this little convenience function it in
so many places (and packages) that this would be a massive amount of
work - doesn't feel justified, given the tiny chance of causing a problem.
Ulrike
Am 08.05.2023 um 14:45 schrieb Hadley Wickham:
If it's internal only, y
If it's internal only, you could change the name to levels_no()?
Hadley
On Mon, May 8, 2023 at 7:28 AM Ulrike Groemping
wrote:
>
> Thanks, Duncan. I appreciate the view that levels.no acts as an S3
> method for the generic levels, if an object of class "no" is handed to
> it. However, as the func
Thanks, Duncan. I appreciate the view that levels.no acts as an S3
method for the generic levels, if an object of class "no" is handed to
it. However, as the function is not intended as an S3 method, it does
not make sense to document it as such. As the function is internal only,
which makes th
There really isn't such a thing as "a function that looks like an S3
method, but isn't". If it looks like an S3 method, then in the proper
circumstances, it will be called as one.
In your case the function name is levels.no, and it isn't exported. So
if you happen to have an object with a cl
Thank your for the solution attempt. However, using the keyword internal
does not solve the problem, the note is still there. Any other proposals
for properly documenting a function that looks like an S3 method, but isn't?
Best, Ulrike
Am 05.05.2023 um 12:56 schrieb Iris Simmons:
You can add
You can add
\keyword{internal}
to the Rd file. Your documentation won't show up the in the pdf manual, it
won't show up in the package index, but you'll still be able to access the
doc page with ?levels.no or help("levels.no").
This is usually used in a package's deprecated and defunct doc pages
16 matches
Mail list logo
