dMZX Forums: Continue, Abort loop labels -> Rejected Requests -> Tracker

I think it'd be more convenient to have some sort of continue and abort loop labels that could be sent in a loop. These labels could reset the stack to where it was when the loop started, e.g. they can be called during subroutines, but that's not really a necessity. This is mostly to save me from having to come up with arbitrary label names every time I need something like this.

Old code:

loop start
if "bart&LOOPCOUNT&" = -1 "bartLoop5Continue"
if "bart&LOOPCOUNT&" = "desiredBartValue" "bartLoop5Abort"
. "bart manipulation here"
. "purposely obtuse logic so I can fit an abort loop in"
if "bart&LOOPCOUNT&" != "otherDesiredBartValue" "bartLoop5Continue"
abort loop
: "bartLoop5Continue"
loop "('barts'-1)"
. "create a new bart since since I didn't like any of the other ones"
inc "barts" 1
: "bartLoop5Abort"
. "do something here"

loop start
if "bart&LOOPCOUNT&" = -1 "$$continue"
if "bart&LOOPCOUNT&" = "bartValue" "$$abort"
. "bart"
. "purposely obtuse logic so I can show an alternative to abort loop"
if "bart&LOOPCOUNT&" = "bartValue#2" "$$continue"
goto "$$abort"
loop "('barts'-1)"
. "create a new bart since *IF* I didn't like any of the other ones"
inc "barts" "('LOOPCOUNT'='barts')"
. "do something here"

Updating status to: Flagged For Future Version
Updating severity to: 1 - Low

Stuff like this is part of Exo's original roadmap apparently. Best save it for when the bytecode changes start rolling in after the switch to debytecode.

Updating status to: Rejected
Updating severity to: 0 - None

We'll handle this without labels in debytecode.

Moving to: Rejected Requests