[squeak-dev] Re: Getting back to push/pop remappable oop
siguctua at gmail.com
Tue Nov 11 17:15:40 UTC 2008
2008/11/11 Igor Stasenko <siguctua at gmail.com>:
> And , since primitive should return only single object, its easy to
> prove, that it requires MAXIMUM SINGLE temp value on stack, which
> needs to be remapped.
btw, from this follows as well, that there is no need in supporting a
bunch of remappable oops.
It really should be only a single remappable oop all the times.
So, instead of push/pop, it can be set/get. And this single value
should be set to nil, or smallint when primitive returns.
But i'm really doubt that it needed at all.
At the stage when primitive generating new object(s), which can be
subject of remapping , a primitive failure is quite unlikely, so
arguments on stack can be overidden.
Igor Stasenko AKA sig.
More information about the Squeak-dev