Hi, I had a need to replace the printOn: implementation in ScaledDecimal so that it didn&#39;t include the scale. �In other words, I don&#39;t want my users to see &#39;3.02s2&#39;. �Being lazy, my first impulse was to remove the code from printOn: that appends the scale, but I realized I&#39;d have to do that every time I upgraded my pharo version.<div>
<br></div><div>Instead I tried to implement a subclass called DisplayableScaledDecimal and override printOn. �That seems straightforward and smalltalky, but when I do math on instances of DisplayableScaledDecimal, the results are converted back to ScaledDecimal. �Now I&#39;m looking at re-implementing all the math logic in scaledDecimal to avoid that.</div>
<div><br></div><div>The problem seems to be in the coerce: method, which reads:</div><div><br></div><div><div>coerce: aNumber</div><div><span class="Apple-tab-span" style="white-space:pre">	</span>&quot;Note: this quick hack could be replaced by double dispatching&quot;</div>
<div><span class="Apple-tab-span" style="white-space:pre">	</span></div><div><span class="Apple-tab-span" style="white-space:pre">	</span>aNumber class = self class ifTrue: [^self class newFromNumber: aNumber scale: (scale max: aNumber scale)].</div>
<div><span class="Apple-tab-span" style="white-space:pre">	</span>(aNumber isFraction or: [aNumber isInteger]) ifTrue: [^self class newFromNumber: aNumber scale: scale].</div><div><span class="Apple-tab-span" style="white-space:pre">	</span>^aNumber</div>
</div><div><br></div><div>I guess I could override coerce:, but that seems wrong.�</div><div><br></div><div>So my question to the smalltalk gods on the list is: Could this be fixed with double dispatching as the comment sort of suggests, and would it be a useful thing to do?</div>
<div><br></div><div><br></div>