Issue 6110 in pharo: removing of a method may need a Compiler

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Issue 6110 in pharo: removing of a method may need a Compiler

pharo
Status: New
Owner: [hidden email]
Labels: Type-Bug

New issue 6110 by [hidden email]: removing of a method may need a  
Compiler
http://code.google.com/p/pharo/issues/detail?id=6110

The current implementation of removing of a mehtod may need a presence of  
the Compiler in case that it works with traits.

We should check why it is required and I we can make it compiler  
independent.

> PharoKernel shrinking report
> Error:
> MessageNotUnderstood: CompiledMethod>>parserClass
> 341 2 BlockClosure>>cull:
> 3 BlockClosure>>cull:cull:
> 4 5 BlockClosure>>cull:
> 6 7 BlockClosure>>ensure:
> 8 MethodContext(ContextPart)>>handleSignal:
> 9 MessageNotUnderstood(Exception)>>signal
> 10 CompiledMethod(Object)>>doesNotUnderstand: #parserClass
> 11 CompiledMethod>>getSourceReplacingSelectorWith:
> 12 ClassDescription class(Behavior)>>addTraitSelector:withMethod:
> 13 14 OrderedCollection>>do:
> 15 ClassDescription class(Behavior)>>updateMethodDictionarySelector:
> 16 17 Array(SequenceableCollection)>>do:
> 18 ClassDescription class(Behavior)>>noteChangedSelectors:
> 19 ClassDescription class(Behavior)>>removeSelector:
> 20 ClassDescription class(ClassDescription)>>removeSelector:
> 21 22 Array(SequenceableCollection)>>do:
> 23 ClassDescription class(ClassDescription)>>removeCategory:
> 24 25 OrderedCollection>>do:
> 26 27 Set>>do:
> 28 SystemNavigation>>removeAllButPackages:
> 29 30 BlockClosure>>on:do:
> 31 BlockClosure>>ifError:
> 32 SmalltalkImage>>privShrinkingProcess
> 33 34


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker