On Sep 7, 2012, at 2:14 PM, Duncan Murdoch <murdoch.dun...@gmail.com> wrote:
> On 07/09/2012 2:00 PM, Simon Urbanek wrote:
>> On Sep 7, 2012, at 12:59 PM, "Warnes, Gregory" <gregory.war...@novartis.com>
>> wrote:
>>
>> >
>> > On 9/7/12 12:55 PM, "Uwe Ligges" <lig...@statistik.tu-dortmund.de> wrote:
>> >
>> >> On 07.09.2012 17:05, Tim Hesterberg wrote:
>> >>> When creating a package, I would like a way to tell R that
>> >>> a function with a period in its name is not a method.
>> >>
>> >> You can't. There are few exception for historic names (S definitions)
>> >> hardcoded in R.
>> >>
>> >
>> > Would it be possible to add a \notmethod{} decorator to allow package
>> > maintainers to avoid these messages?
>> >
>>
>> I would strongly support any solution since it has bitten me as well...
>
> An alternative would be to say that if it's not declared to be a method in
> the NAMESPACE file, it's not one.
Yes, that's what I was expecting in the first place ...
(BTW: \function{} may be more natural than \notmethod{})
> I think that would actually be more work though, since it would probably
> break a lot of packages...
>
I wonder - those would already get a warning that they don't declare S3 methods
properly so it may not be as surprising. Moreover it won't actually break
anything at this point, just silence some warnings (unless we get to
distinguish S3 methods from functions in S3 dispatch, but I last time I was
told we are not anywhere close to a solution on that one ...).
______________________________________________
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
