[Vm-dev] Integer comparition primitive failures on Cog
eliot.miranda at gmail.com
Mon May 2 19:52:15 UTC 2011
On Mon, May 2, 2011 at 12:39 PM, Igor Stasenko <siguctua at gmail.com> wrote:
> On 2 May 2011 18:11, Eliot Miranda <eliot.miranda at gmail.com> wrote:
> > 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.
> compact classes are pain in the ...
> so i would not cry if we get rid of them. but right now i see that
> potentially i could break things if i start replacing one
> compact class with another.
Doctor, doctor, it hurts when I...
Doctor: don't do that.
> > 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.
> Best regards,
> Igor Stasenko AKA sig.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Vm-dev