Hi guys. We were discussing in <a href="http://code.google.com/p/pharo/issues/detail?id=5748">http://code.google.com/p/pharo/issues/detail?id=5748</a><br>The thing is that Traits are depenending on Ring. And I don&#39;t really like that. If you do a simple #addToComposition:� you end up calling Ring.<br>
<br>The problematic method is:<br><br>TraitDescription &gt;&gt; #collectMethodsFor: aSelector into: methodDescription<br>��� <br>��� (self includesSelector: aSelector) ifTrue: [ <br>��� ��� methodDescription addLocatedMethod: (<br>
��� ��� ��� RGMethodDefinition<br>��� ��� ��� ��� realClass: self<br>��� ��� ��� ��� selector: aSelector)]<br clear="all"><br><br>which uses RGMethodDefinition. <br><br>Previously (before Ring) it was using LocatedMethod (which was removed)<br>
<br>collectMethodsFor: aSelector into: methodDescription<br>��� (self includesSelector: aSelector) ifTrue: [ <br>��� ��� methodDescription addLocatedMethod: (<br>��� ��� ��� LocatedMethod<br>��� ��� ��� ��� location: self<br>
��� ��� ��� ��� selector: aSelector)]<br><br><br>I attach a PharoDebug.log with a halt in  #collectMethodsFor:into:� so that you can see all the stack.<br><br>This is the reason why FuelPackageLoader depends on Ring, just for the traits when we do the #addToComposition:. <br>
<br>So...what do we do?� we just accept the depedency? <br><br>cheers<br><br><br>-- <br>Mariano<br><a href="http://marianopeck.wordpress.com" target="_blank">http://marianopeck.wordpress.com</a><br><br>