Return - Revision history

Doom64hunter at 12:20, 7 January 2024

2024-01-07T12:20:22Z

← Older revision		Revision as of 05:20, 7 January 2024
Line 1:		Line 1:
	A '''return''' command is similar to '''[[break]]''' in that it stops code after the '''return''' from executing and thus can be used to exit a state early. However, a '''return''' propagates along a call chain of [[state]]s and terminates the execution of the innermost [[event]] or [[actor]] code. Thus, when the following code snippet is run, only quote 125 ("SPAWNED HEAVYHBOMB") is displayed.		A '''return''' command is similar to '''[[break]]''' in that it stops code after the '''return''' from executing and thus can be used to exit a state early.

	~~See also~~ [[~~break~~]].		However, a '''return''' propagates along a call chain of [[state]]s and terminates the execution of the innermost [[event]] or [[actor]] code.

			To only exit the current state instead of the whole chain, instead use the [[terminate]] command.

	Not to be confused with the [[RETURN]] gamevar and [[return (userdef)\|return (userdef structure)]].		Not to be confused with the [[RETURN]] gamevar and [[return (userdef)\|return (userdef structure)]].

	== Examples ==		== Examples ==

			When the following code snippet is run, only quote 125 ("SPAWNED HEAVYHBOMB") is displayed.

	'''definequote''' 125 SPAWNED HEAVYHBOMB		'''definequote''' 125 SPAWNED HEAVYHBOMB

Fox at 08:24, 20 February 2020

2020-02-20T08:24:46Z

← Older revision		Revision as of 01:24, 20 February 2020
Line 1:		Line 1:
	A '''return''' command is similar to '''[[break]]''' in that it stops code after the '''return''' from executing and thus can be used to exit a state early. However, a '''return''' propagates along a call chain of [[state]]s and terminates the execution of the innermost [[event]] or [[actor]] code. Thus, when the following code snippet is run, only quote 125 ("SPAWNED HEAVYHBOMB") is displayed.		A '''return''' command is similar to '''[[break]]''' in that it stops code after the '''return''' from executing and thus can be used to exit a state early. However, a '''return''' propagates along a call chain of [[state]]s and terminates the execution of the innermost [[event]] or [[actor]] code. Thus, when the following code snippet is run, only quote 125 ("SPAWNED HEAVYHBOMB") is displayed.

			See also [[break]].

			Not to be confused with the [[RETURN]] gamevar and [[return (userdef)\|return (userdef structure)]].

			== Examples ==

	'''definequote''' 125 SPAWNED HEAVYHBOMB		'''definequote''' 125 SPAWNED HEAVYHBOMB

Hendricks266 at 03:10, 4 April 2015

2015-04-04T03:10:19Z

← Older revision		Revision as of 20:10, 3 April 2015
Line 28:		Line 28:

	Replacing the '''return''' by a '''[[break]]''' in the above example would lead to quotes 126 and 125 being displayed (in that order) at run time.		Replacing the '''return''' by a '''[[break]]''' in the above example would lead to quotes 126 and 125 being displayed (in that order) at run time.

			[[Category:Event manipulation]]

Hendricks266 at 20:31, 31 January 2014

2014-01-31T20:31:45Z

← Older revision		Revision as of 13:31, 31 January 2014
Line 1:		Line 1:
	A '''return''' command is similar to '''[[break]]''' in that it stops code after the '''return''' from executing and thus can be used to exit a state early. However, a '''return''' ~~proparates~~ along a call chain of [[state]]s and terminates the execution of the innermost [[event]] or [[actor]] code. Thus, when the following code snippet is run, only quote 125 ("SPAWNED HEAVYHBOMB") is displayed.		A '''return''' command is similar to '''[[break]]''' in that it stops code after the '''return''' from executing and thus can be used to exit a state early. However, a '''return''' propagates along a call chain of [[state]]s and terminates the execution of the innermost [[event]] or [[actor]] code. Thus, when the following code snippet is run, only quote 125 ("SPAWNED HEAVYHBOMB") is displayed.

	'''definequote''' 125 SPAWNED HEAVYHBOMB		'''definequote''' 125 SPAWNED HEAVYHBOMB

TX at 19:10, 23 December 2012

2012-12-23T19:10:13Z

← Older revision		Revision as of 12:10, 23 December 2012
Line 1:		Line 1:
	A '''return''' command is similar to '''[[break]]''' in that it stops code after the '''return''' from executing and thus can be used to exit a state early. However, a '''return''' proparates along a call chain of [[state]]s and terminates the execution of the innermost [[event]] or [[actor]] code. Thus, when the following code snippet is run, only quote 125 ("SPAWNED ~~LIGHTEFFECT1~~") is displayed.		A '''return''' command is similar to '''[[break]]''' in that it stops code after the '''return''' from executing and thus can be used to exit a state early. However, a '''return''' proparates along a call chain of [[state]]s and terminates the execution of the innermost [[event]] or [[actor]] code. Thus, when the following code snippet is run, only quote 125 ("SPAWNED HEAVYHBOMB") is displayed.

	'''definequote''' 125 SPAWNED HEAVYHBOMB		'''definequote''' 125 SPAWNED HEAVYHBOMB

Helixhorned: clarify a little more

2012-12-23T18:36:30Z

clarify a little more

← Older revision		Revision as of 11:36, 23 December 2012
Line 1:		Line 1:
	A '''return''' command is similar to '''[[break]]''' in that it stops code after the '''return''' from executing and thus can be used to exit a state early. However, a '''return''' proparates along a call chain of [[state]]s, ~~so that~~ when the following code snippet is run, only quote 125 ("SPAWNED LIGHTEFFECT1") is displayed.		A '''return''' command is similar to '''[[break]]''' in that it stops code after the '''return''' from executing and thus can be used to exit a state early. However, a '''return''' proparates along a call chain of [[state]]s and terminates the execution of the innermost [[event]] or [[actor]] code. Thus, when the following code snippet is run, only quote 125 ("SPAWNED LIGHTEFFECT1") is displayed.

	'''definequote''' 125 SPAWNED HEAVYHBOMB		'''definequote''' 125 SPAWNED HEAVYHBOMB

Helixhorned: make example run with vanilla EDuke32

2012-12-23T18:33:20Z

make example run with vanilla EDuke32

← Older revision		Revision as of 11:33, 23 December 2012
Line 1:		Line 1:
	A '''return''' command is similar to '''[[break]]''' in that it stops code after the '''return''' from executing and thus can be used to exit a state early. However, a '''return''' proparates along a call chain of [[state]]s, so that when the following code snippet is run, only quote 125 ("SPAWNED LIGHTEFFECT1") is displayed.		A '''return''' command is similar to '''[[break]]''' in that it stops code after the '''return''' from executing and thus can be used to exit a state early. However, a '''return''' proparates along a call chain of [[state]]s, so that when the following code snippet is run, only quote 125 ("SPAWNED LIGHTEFFECT1") is displayed.

	'''definequote''' 125 SPAWNED ~~LIGHTEFFECT1~~		'''definequote''' 125 SPAWNED HEAVYHBOMB
	'''definequote''' 126 RAN EVENT_EGS		'''definequote''' 126 RAN EVENT_EGS
	'''definequote''' 127 RAN TEST STATE		'''definequote''' 127 RAN TEST STATE
Line 11:		Line 11:

	'''onevent''' [[EVENT_EGS]]		'''onevent''' [[EVENT_EGS]]
	ifactor ~~LIGHTEFFECT1~~		ifactor HEAVYHBOMB
	{		{
	state teststate1 ''// after teststate1's return, return from EVENT_EGS!''		state teststate1 ''// after teststate1's return, return from EVENT_EGS!''
Line 22:		Line 22:
	{		{
	''// the concrete actor is irrelevant, only placeholder''		''// the concrete actor is irrelevant, only placeholder''
	[[spawn]] ~~LIGHTEFFECT1~~ ''// --> EVENT_EGS''		[[spawn]] HEAVYHBOMB ''// --> EVENT_EGS''
	userquote 125		userquote 125
	}		}

Helixhorned: wording

2012-05-10T22:32:05Z

wording

← Older revision		Revision as of 15:32, 10 May 2012
Line 1:		Line 1:
	A '''return''' command is similar to '''[[break]]''' in that it ~~can be used to stop~~ code after the '''return''' from executing and thus can be used to exit a state early. However, a '''return''' proparates along a call chain of [[state]]s, so that when the following code snippet is run, only quote 125 ("SPAWNED LIGHTEFFECT1") is displayed.		A '''return''' command is similar to '''[[break]]''' in that it stops code after the '''return''' from executing and thus can be used to exit a state early. However, a '''return''' proparates along a call chain of [[state]]s, so that when the following code snippet is run, only quote 125 ("SPAWNED LIGHTEFFECT1") is displayed.

	'''definequote''' 125 SPAWNED LIGHTEFFECT1		'''definequote''' 125 SPAWNED LIGHTEFFECT1

Helixhorned: Add "return" page based on "break" and clarify differences. Might need more exact definitions where control-flow flags are reset and where not.

2012-05-10T22:31:33Z

Add "return" page based on "break" and clarify differences. Might need more exact definitions where control-flow flags are reset and where not.

New page

A '''return''' command is similar to '''[[break]]''' in that it can be used to stop code after the '''return''' from executing and thus can be used to exit a state early. However, a '''return''' proparates along a call chain of [[state]]s, so that when the following code snippet is run, only quote 125 ("SPAWNED LIGHTEFFECT1") is displayed.

'''definequote''' 125 SPAWNED LIGHTEFFECT1
'''definequote''' 126 RAN EVENT_EGS
'''definequote''' 127 RAN TEST STATE

'''state''' teststate1
return
userquote 127
'''ends'''

'''onevent''' [[EVENT_EGS]]
ifactor LIGHTEFFECT1
{
state teststate1 ''// after teststate1's return, return from EVENT_EGS!''
userquote 126
}
'''endevent'''

'''onevent''' [[EVENT_LOADACTOR]]
ifvare THISACTOR 0
{
''// the concrete actor is irrelevant, only placeholder''
[[spawn]] LIGHTEFFECT1 ''// --> EVENT_EGS''
userquote 125
}
'''endevent'''

Replacing the '''return''' by a '''[[break]]''' in the above example would lead to quotes 126 and 125 being displayed (in that order) at run time.