[Cuis-dev] Changes to unwind logic and termination

[Juan Vuletich]

Hi Jaromir,

On 2025-11-20 10:37 AM, Jaromir Matas via Cuis-dev wrote:
> ...
>
>>> What still confuses me
>>> is when you debug
>>>   
>>> `true not`
>>>   
>>> then step into #not and explore thisContext: what's the meaning of the
>>> pc counter relative to the method? It doesn't point to an existing
>>> bytecode (there's none actually) - is it ok? Why 25? It's confusing...
>>   
>> Well, it is a primitive method, the first (and only) bytecode there is
>> the 3 byte "Call Primitive" bytecode, at position 25. Maybe some
>> clarification is needed somewhere.
>>   
> It's clear now, I could have known better though :) I've enclosed the
> explorer screenshot I found confusing/inconsistent. The pc says 25 but
> there's no bytecode 25; they start at 28. Of course the last literal is
> literal2 so the next must refer to the three byte bytecode conveniently
> translated to "symbolic: Quick return false" but it's quite a lot to
> realize without prior experience ;o
>
>> ...

Well, you're right. The inspector was slightly better though...

Based on your experience and feedback I changed how bytecodes for 
methods are shown in Browser, Explorer and Inspector. I hope it is 
clearer now!

Cheers,

-- 
Juan Vuletich
www.cuis.st
github.com/jvuletich
researchgate.net/profile/Juan-Vuletich
independent.academia.edu/JuanVuletich
patents.justia.com/inventor/juan-manuel-vuletich