Difference between revisions of "Parallel (API)"

From ComputerCraft Wiki
Jump to: navigation, search
m (Expanded)
m
Line 3: Line 3:
 
Parallel is an API which allows you to multitask.
 
Parallel is an API which allows you to multitask.
  
The functions are not actually executed simultaniously, but rather this API will automatically switch between them whenever they yield (eg whenever they call [[coroutine.yield]](), or functions that call that - eg [[os.pullEvent]]() - or functions that call that, etc - basically, anything that causes the function to "pause").
+
Functions are not actually executed simultaniously, but rather this API will automatically switch between them whenever they yield (eg whenever they call [[coroutine.yield]](), or functions that call that - eg [[os.pullEvent]]() - or functions that call that, etc - basically, anything that causes the function to "pause").
  
 
Each function executed in "parallel" gets its own copy of the event queue, and so "event consuming" functions (again, mostly anything that causes the script to pause - eg [[sleep]](), [[rednet.receive]](), most of the [[Turtle (API)|turtle API]], etc) can safely be used in one without affecting the event queue accessed by the other.
 
Each function executed in "parallel" gets its own copy of the event queue, and so "event consuming" functions (again, mostly anything that causes the script to pause - eg [[sleep]](), [[rednet.receive]](), most of the [[Turtle (API)|turtle API]], etc) can safely be used in one without affecting the event queue accessed by the other.

Revision as of 18:15, 10 April 2014

This page needs some serious TLC, stat!
Please help us by cleaning it, fixing it up, or sparing it some love.
(Reason: This API needs explanation and examples. MKlegoman357 20:41, 6 April 2014 (GMT))

Parallel is an API which allows you to multitask.

Functions are not actually executed simultaniously, but rather this API will automatically switch between them whenever they yield (eg whenever they call coroutine.yield(), or functions that call that - eg os.pullEvent() - or functions that call that, etc - basically, anything that causes the function to "pause").

Each function executed in "parallel" gets its own copy of the event queue, and so "event consuming" functions (again, mostly anything that causes the script to pause - eg sleep(), rednet.receive(), most of the turtle API, etc) can safely be used in one without affecting the event queue accessed by the other.

Grid disk.png  Parallel (API)
Function Return values Description
parallel.waitForAny(function1, function2, ...) number stoppedFunction Runs all the functions at the same time, and stops when any of them returns.
parallel.waitForAll(function1, function2, ...) nil Runs all the functions at the same time, and stops when all of them have returned.