RPL equivalents to BREAK, CYCLE, EXIT, etc.?

[Dave Britten]

My 2¢ (not really addressed at anybody in particular): BREAK, CONTINUE, and even the occasional GOTO are a hell of a lot less damaging to code clarity than the extensive stackrobatics and mental juggling that the RPL system encourages. It takes a lot of discipline to write RPL code that isn't totally opaque even coming back to it yourself later in the day, and it's often done at the expense of performance.

RPL is nice, but it certainly wouldn't have killed them to add some more branching.