Synchronous concurrency: Difference between revisions

Content added Content deleted

Inline

Revision as of 21:03, 12 August 2010 (view source) Ce (talk \| contribs) (requires concurrency) ← Older edit		Revision as of 03:09, 18 August 2010 (view source) rosettacode>Coderjoe m (use the Requires template) Newer edit →
Line 1:		Line 1:
	{{task\|Concurrency}}[[requires::Capability:Concurrency~~\| ]]~~		{{task\|Concurrency}}{{requires\|Capability:Concurrency}}
	The goal of this task is to create two concurrent activities ("[[Thread\|Threads]]" or "Tasks", not [[Process\|processes]].) that share data synchronously. Your language may provide syntax or libraries to perform concurrency. Different languages provide different implementations of concurrency, often with different names. Some languages use the term threads, others use the term tasks, while others use co-processes. This task should not be implemented using fork, spawn, or the [[Linux]]/[[UNIX]]/[[Windows\|Win32]] pipe command, as communication should be between threads, not processes.		The goal of this task is to create two concurrent activities ("[[Thread\|Threads]]" or "Tasks", not [[Process\|processes]].) that share data synchronously. Your language may provide syntax or libraries to perform concurrency. Different languages provide different implementations of concurrency, often with different names. Some languages use the term threads, others use the term tasks, while others use co-processes. This task should not be implemented using fork, spawn, or the [[Linux]]/[[UNIX]]/[[Windows\|Win32]] pipe command, as communication should be between threads, not processes.