[Pharo-dev] [update 3.0] #30449

Marcus Denker marcus.denker at inria.fr
Fri Oct 4 08:57:04 EDT 2013


11777 Fix SpecTests
11776 Fix Create action on #subclassResponsibility

The debugger now displays the create button when an exception of type #subclassResponsibility is shown. However this action should only be shown if we are not working with an object of the abstract class (yes, normally it should not happen). Also all possible superclasses in which the method can be added should be displayed:
for example consider this hierarchy:
  -> Child1
    -> Child11
        -> Child111
  self subclassResponsibility 

In this case 'Parent new doSomething' should not add a create action in the debugger.
'Child1 new doSomething' should automatically implement the method in the class Child1
'Child3 new doSomething' should allow the user to select if he wants to add the method in classes Child1, Child2 or Child3. 
In all cases traits should be taken into account.

Diff information:

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 203 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20131004/3de62d35/attachment.asc>

More information about the Pharo-dev mailing list