Update UnloadReference to use new virtual frame.

Update UnloadReference to use new virtual frame.

[William Hesse, 2008-12-29 10:43:55]

Here is a small change, testing whether development on the Mac works.  Tested
with regular tests, but not Mozilla.  Should I make a "ReplaceTop" rather than
the drop, push sequence?

[Kevin Millikin (Chromium), 2008-12-29 11:00:52]

I would go with even less external manipulation.  What's happening (dropping
some elements immediately below the frame top while preserving the top) seems
like a purely frame-internal operation.

Forth programmers would call it "nip".  We could use that name and we could
allow it to take a non-negative integer argument that was the number of elements
to nip.

[William Hesse, 2008-12-29 19:23:27]

I guess it doesn't hurt anything to add it.  I'll do that, as well as the other
changes from the previous list.


On 2008/12/29 11:00:52, Kevin Millikin wrote:
> I would go with even less external manipulation.  What's happening (dropping
> some elements immediately below the frame top while preserving the top) seems
> like a purely frame-internal operation.
> 
> Forth programmers would call it "nip".  We could use that name and we could
> allow it to take a non-negative integer argument that was the number of
elements
> to nip.