2008/11/10 Stéphane Ducasse <[EMAIL PROTECTED]>: > Hi keith > >>>> We had Kerala loaded when we committed this SUnit version, but Kerala >>> >>> overrides method in SUnit such as TestResult>>runCase:, so those >>> methods didn't get committed. Very bad. >> >> Not bad, typical, and you get used to it winding you up if you are an >> MC1.0 user. So you have to adopt a strategy for maintaining each >> package, such as maintainng an image specifically for each package that >> you may have overrides in. >> >> So that is what MC1.5 was written for, to fix this bug! But people have >> failed to see the need for it. >> >> Because many of you folks are package writers, rather than package >> users/tweakers you don't find this problem an issue. But if the package >> writer will not take on board requests for modifications what can you do. > > You lost me. > Could reexplained it to me> May be I'm just too tired too :) >
Let me elaborate. Suppose there is two persons A and B. Both are using package C. And both want to override some methods in package C to make their packages working. But author of package C refusing to include modifications of both persons. Now, the only option they have is to ship their MC package each with own overrides to original 'maintained' version of C, and hope that if someone would want to load both A and B packages, their overrides will not interfere with each other. -- Best regards, Igor Stasenko AKA sig.
_______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
