Le 30/05/2013 14:09, Stéphane Ducasse a écrit :
On May 30, 2
Yes. I can say true become: false, too.
Overrides can be interesting as a temperer hack. E.g. in Opal development, I
might add an override just to test. Then loading Opal makes
the image package dirty. So later, when I know what I want, I will move that
change to the image.
You should not use overrides as a concept in delivered software (as it does not
work), so modeling it is wrong as then people will use it.
Yes making it impossible is not nice either, because temporarily I want to be
able to just do it, like I can do all sorts of things.
So this is more something we should add a rule for in Code Crititque…
I'm not sure. Because something you really need them.
I'd be worried then.
Either we have a need for extension where only an override will do...
Then why not modeling it and critique it when appropriate? Hiding it
under an extension won't make the problem disappear, it will just hide it.
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
