On May 29, 2013, at 9:04 AM, Goubier Thierry <[email protected]> wrote:
> Le 28/05/2013 22:23, stephane ducasse a écrit :
>>
>>
>>> I have a question about RPackage and overrides.
>>>
>>> RPackage consider that an override method is an extension, right?
>>
>> for RPackage a package is a list of method definitions and class definition.
>> There is no specific tagging for overriding methods that would magically
>> reappear when
>> their overriding method would be unloaded.
>
> Ok. But in MC, a MethodDefinition has a way of telling if it is an override
> or not. RPackage does not (and list -overrides as extensions, as for example
> in Keymapping).
>
>> I do not know if this answer your question.
>
> Not sure :) I wondered if I should bother with overrides or let them as
> extensions, as RPackage seems to be considering them the same.
>
> What do you think? Is it important to classify overrides as such, or just let
> them be extensions ?
The thing is that overrides don't work. As soon as 2 packages override the same
method ==> which one is it?
Therefore, overrides as a *concept* make no sense. And thus modeling them makes
no sense.
Nobody ever should do overrides, because it will just not work as soon as it is
used a lot.
Marcus
