Talk:Coroutine (API) - Revision history

Lyqyd at 14:04, 28 May 2013

2013-05-28T14:04:39Z

Hawk777 at 13:41, 28 May 2013

2013-05-28T13:41:22Z

Lyqyd: Created page with "Bottom section (Interaction with other APIs) is written upside-down. It would be more useful to start out talking about how the event-based model ComputerCraft uses actually u..."

2013-05-28T11:53:51Z

Created page with "Bottom section (Interaction with other APIs) is written upside-down. It would be more useful to start out talking about how the event-based model ComputerCraft uses actually u..."

New page

Bottom section (Interaction with other APIs) is written upside-down. It would be more useful to start out talking about how the event-based model ComputerCraft uses actually utilizes coroutines and the .yield and .resume parameters and return values. That is the primary use case for coroutines in ComputerCraft, so it would be better to lead with that, as it will cause less confusion among new users. From there, it would be good to mention that if one does desire to deviate from the event-based model ComputerCraft uses, that one should avoid using (or add special handling for) all of the functions which wait for events. "Blocking" is also a misleading term, since it implies that the execution point gets stuck in that function (which would block other coroutines from running), when the truth of the matter is that it simply yields execution. "Yielding" would be a better term. [[User:Lyqyd|Lyqyd]] 15:53, 28 May 2013 (MSK)

← Older revision		Revision as of 14:04, 28 May 2013
Line 2:		Line 2:

	:Better? [[User:Hawk777\|Hawk777]] 17:41, 28 May 2013 (MSK)		:Better? [[User:Hawk777\|Hawk777]] 17:41, 28 May 2013 (MSK)
		+
		+	::Much better, thanks! [[User:Lyqyd\|Lyqyd]] 18:04, 28 May 2013 (MSK)

← Older revision		Revision as of 13:41, 28 May 2013
Line 1:		Line 1:
	Bottom section (Interaction with other APIs) is written upside-down. It would be more useful to start out talking about how the event-based model ComputerCraft uses actually utilizes coroutines and the .yield and .resume parameters and return values. That is the primary use case for coroutines in ComputerCraft, so it would be better to lead with that, as it will cause less confusion among new users. From there, it would be good to mention that if one does desire to deviate from the event-based model ComputerCraft uses, that one should avoid using (or add special handling for) all of the functions which wait for events. "Blocking" is also a misleading term, since it implies that the execution point gets stuck in that function (which would block other coroutines from running), when the truth of the matter is that it simply yields execution. "Yielding" would be a better term. [[User:Lyqyd\|Lyqyd]] 15:53, 28 May 2013 (MSK)		Bottom section (Interaction with other APIs) is written upside-down. It would be more useful to start out talking about how the event-based model ComputerCraft uses actually utilizes coroutines and the .yield and .resume parameters and return values. That is the primary use case for coroutines in ComputerCraft, so it would be better to lead with that, as it will cause less confusion among new users. From there, it would be good to mention that if one does desire to deviate from the event-based model ComputerCraft uses, that one should avoid using (or add special handling for) all of the functions which wait for events. "Blocking" is also a misleading term, since it implies that the execution point gets stuck in that function (which would block other coroutines from running), when the truth of the matter is that it simply yields execution. "Yielding" would be a better term. [[User:Lyqyd\|Lyqyd]] 15:53, 28 May 2013 (MSK)
		+
		+	:Better? [[User:Hawk777\|Hawk777]] 17:41, 28 May 2013 (MSK)