Busyloop - Revision history

Kuroneko at 05:02, 27 July 2012

2012-07-27T05:02:14Z

← Older revision		Revision as of 05:02, 27 July 2012
Line 3:		Line 3:
	. "do some code here"		. "do some code here"
	goto "loop"</tt>		goto "loop"</tt>
	More specifically, this term often refers to a loop like the previous one that does not have an explicit [[cycle]] terminator, and thus does more work than it should per cycle. In the past this wasn't a big deal and had few negative effects, since the [[commands]]-per-cycle limit of 40 forced execution to move to the next robot fairly quickly. Since the addition of the "commands" counter, which can variably set this number into the billions, a loop like this becomes a far more serious problem, and can easily cause a game to hang. For this reason, it is recommended that all busyloops contain either of the commands "[[wait 1]]" or "[[cycle]] 1" at some point in their execution. Usually the best place is right after the loop label, if there are multiple points of return; or right before the "goto" command if there is only one.		More specifically, this term often refers to a loop like the previous one that does not have an explicit [[cycle]] terminator, and thus does more work than it should per cycle. In the past this wasn't a big deal and had few negative effects, since the [[commands]]-per-cycle limit of 40 forced execution to move to the next robot fairly quickly. Since the addition of the "commands" counter, which can variably set this number into the billions, a loop like this becomes a far more serious problem, and can easily cause a game to hang. For this reason, it is recommended that all busyloops contain either of the commands "[[wait]] 1" or "[[cycle]] 1" at some point in their execution. Usually the best place is right after the loop label, if there are multiple points of return; or right before the "goto" command if there is only one.

	[[Category:MegaZeux]]		[[Category:MegaZeux]]

Kuroneko at 05:01, 27 July 2012

2012-07-27T05:01:36Z

← Older revision		Revision as of 05:01, 27 July 2012
Line 3:		Line 3:
	. "do some code here"		. "do some code here"
	goto "loop"</tt>		goto "loop"</tt>
	More specifically, this term often refers to a loop like the previous one that does not have an explicit [[cycle]] terminator, and thus does more work than it should per cycle. In the past this wasn't a big deal and had few negative effects, since the [[commands]]-per-cycle limit of 40 forced execution to move to the next robot fairly quickly. Since the addition of the "commands" counter, which can variably set this number into the billions, a loop like this becomes a far more serious problem, and can easily cause a game to hang. For this reason, it is recommended that all busyloops contain the ~~command~~ "cycle 1" at some point in their execution. Usually the best place is right after the loop label, if there are multiple points of return; or right before the "goto" command if there is only one.		More specifically, this term often refers to a loop like the previous one that does not have an explicit [[cycle]] terminator, and thus does more work than it should per cycle. In the past this wasn't a big deal and had few negative effects, since the [[commands]]-per-cycle limit of 40 forced execution to move to the next robot fairly quickly. Since the addition of the "commands" counter, which can variably set this number into the billions, a loop like this becomes a far more serious problem, and can easily cause a game to hang. For this reason, it is recommended that all busyloops contain either of the commands "[[wait 1]]" or "[[cycle]] 1" at some point in their execution. Usually the best place is right after the loop label, if there are multiple points of return; or right before the "goto" command if there is only one.

	[[Category:MegaZeux]]		[[Category:MegaZeux]]

Wervyn: New, short explanation of busyloops

2009-01-29T23:53:37Z

New, short explanation of busyloops

New page

In [[MegaZeux]] parlance, a '''busyloop''' is any program loop designed to execute continuously during the game, such as:<tt>
: "loop"
. "do some code here"
goto "loop"</tt>
More specifically, this term often refers to a loop like the previous one that does not have an explicit [[cycle]] terminator, and thus does more work than it should per cycle. In the past this wasn't a big deal and had few negative effects, since the [[commands]]-per-cycle limit of 40 forced execution to move to the next robot fairly quickly. Since the addition of the "commands" counter, which can variably set this number into the billions, a loop like this becomes a far more serious problem, and can easily cause a game to hang. For this reason, it is recommended that all busyloops contain the command "cycle 1" at some point in their execution. Usually the best place is right after the loop label, if there are multiple points of return; or right before the "goto" command if there is only one.

[[Category:MegaZeux]]