On 5 mai 2010, at 15:41, Igor Stasenko wrote: > Hello, > > there is a certain critial places in system, which should not be > overridden by external packages. > Otherwise, it becomes a mess and usually leads to malfunction in key > system parts: compiler, special objects etc. > > I'd like to propose to introduce a special marker pragma for methods, > which should _never_ be overridden by external package. > > myMethod > <doNotOverride> > > an MC code loader should honor this pragma, and do not attempt to > override this method when installing a package > or at least ask user that there is a risk of getting serious problems, > if you override this method.
I think that the MC loader should ALWAYS warn user when an extension attempts an override, and let him choose (especially as the system does not allow to revert an override for now). Unfortunately the feature has been broken for long. Damien C proposed a solution a long time ago but it didn't work for me. Perhaps the bug is more subtle. -- Simon _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
