[Vm-dev] Integer comparition primitive failures on Cog

[Eliot Miranda]

No.  Instead certain compact incomes should be mandated.  It is absurd to throw away performance and expend effort supporting complexity for flexibility that is essentially never used and in maintaining a scheme that is only partially effective.

Eliot (phone)

On May 2, 2011, at 7:20 AM, Igor Stasenko <siguctua at gmail.com> wrote:

> 
> On 2 May 2011 15:46, Igor Stasenko <siguctua at gmail.com> wrote:
>> Btw,
>> 
>> i don't like this code:
>> 
>>        self assertClassOf: floatOrInt
>>                is: (objectMemory splObj: ClassFloat)
>>                compactClassIndex: ClassFloatCompactIndex.
>> 
> 
> btw, Cog is suspectible to have bugs if during run time you will
> change a class to be no longer compact or
> (and then installing a different class to be compact on same compact
> classes array index as before).
> 
> To avoid that, there should be a primitive which should refresh
> compact indices for most used classes,
> to avoid bugs.
> 
> (The StackInterpreter>>checkAssumedCompactClasses should be run each
> time when some class become (un)compact).
> 
> -- 
> Best regards,
> Igor Stasenko AKA sig.