Le 29/05/2013 23:16, stephane ducasse a écrit :
On May 29, 2013, at 9:08 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.
We do not support this "feature" since it is bogus since years.
Then you just have to ensure that integration rejects overrides (and
that the IDE does as well: I'm sure I can create overrides in Pharo,
isn't it?).
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 ?
just extensions.
Makes my life simpler ;)
Thierry
--
Thierry Goubier
CEA list
Laboratoire des Fondations des Systèmes Temps Réel Embarqués
91191 Gif sur Yvette Cedex
France
Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
