Hi Chris,


> On Mar 31, 2017, at 1:09 PM, Chris Muller <asqueaker at gmail.com> wrote:
> 
> Crazy that *I* would suggest something like this but...  could it have
> been needed for the simulator?

Hmm, perhaps.  I expect it is much more likely to do with a serialization framework in which SmallInteger is modeled as a single slot object.  This approach would also bridge between the old non-immediate and new immediate Charater representations.

> 
>> On Wed, Mar 29, 2017 at 1:32 PM, Eliot Miranda <eliot.miranda at gmail.com> wrote:
>> Hi All,
>> 
>>    another dubious piece of code is this:
>> 
>> SmallInteger>>instVarAt: i
>> "Small integer has to be specially handled."
>> 
>> i = 1 ifTrue: [^self].
>> self error: 'argument too big for small integer instVarAt:'
>> 
>> Either this is important and should be replicated in Character and
>> SmallFloat64 (the other two immediate classes) or it should be discarded.
>> It's ancient (pre version stamps).  I vote to nuke it.  Opinions?
>> _,,,^..^,,,_
>> best, Eliot
>> 
>> 
>> 
>