Can 50g sysRPL jump to lables?

[DavidM]

(10-30-2018 03:36 PM)3298 Wrote:  Well, there is COLA_EVAL. I think the Nosy Readme even mentions it. It has the side effect of EVALing level 1 of the data stack, but many objects put themselves right back onto the stack. If the preceding code guarantees one of those occupies that level, you're good to go.

Excellent choice! It's very efficient and fast.

If EVALing the object isn't acceptable, another option might be:

Code:

:: RDROPCOLA NOP ;

[3298]

(10-30-2018 04:51 PM)DavidM Wrote:  Excellent choice! It's very efficient and fast.

If EVALing the object isn't acceptable, another option might be:

Code:

:: RDROPCOLA NOP ;

Why not just

Code:

:: RDROP ;

?

[DavidM]

(10-30-2018 04:54 PM)3298 Wrote:  

(10-30-2018 04:51 PM)DavidM Wrote:  Excellent choice! It's very efficient and fast.

If EVALing the object isn't acceptable, another option might be:

Code:

:: RDROPCOLA NOP ;

Why not just

Code:

:: RDROP ;

?

Of course! I was too fixated on the COLA and missed the obvious.

There's also a few other options for specific situations:

RDROPTRUE_: Adds TRUE to the stack as well as the RDROP.
RDROPFALSE_: Adds FALSE to the stack as well as the RDROP.
NoAttn?Semi: Performs the RDROP as long as the ATTN key has not been pressed, but keeps processing the current stream otherwise.
PTR 2BD10: Performs RDROP DROP on a v2.15 system. Not sure about other releases.