Talk:Synchronous concurrency: Difference between revisions

 
(4 intermediate revisions by 3 users not shown)
Line 10:
::::Now it is much clearer. Should there be a similar task that allows communication between processes? The [[Fork Process]] is the closest I can find, but doesn't involve communication. [[User:Ahy1|Ahy1]] 23:11, 21 October 2007 (MDT)
::::Communication between processes is always an operating system feature. Some languages such as Shell provide built-in communication through pipes, which were originally a Unix feature. Other forms of inter-process communication should include signals, semaphores, message queues, and in at least one operating system, message files. Implementations of pipes, for instance, will be fundamentally the same for all languages. The reason for that is that the API for any given Operating System is fixed for all languages. I do not think such a task will reveal very much about languages. [[User:Waldorf|Waldorf]] 19:30, 4 November 2007 (MST)
::::: I have added the Unix Pipes example, and it does reveal some thing about the language, as its usage defines the language :) perhaps It should be allowed? Also the distinction you seem to be making is probably better put as between shared state concurrency and message passing concurrency, as the syntax and semantics of the language may not rely on the exact same operating system features every time (For e.g if I implement bash over JVM, I would not be using pipes, but that would not be visible to the user.). [[User:Rahul|Rahul]] 13:54, 15 April 2008 (MDT)
 
== Python ==
Line 59 ⟶ 60:
 
:Obviously you can write this in many complecated ways, but here we need the simplest way that conform with the task description and is a good example of using Python for this task.
 
== Message passing ==
 
It seems to me many examples don't request the line count from the printer thread, instead maintaining state on their own. Should they be labelled incorrect? [[User talk:foobie-bletch|Foobie Bletch]] 16:21, 11 August 2009 (UTC)
 
== Illegal Character in ALGOL 68 Example ==
 
I see that there's at least several characters in the ALGOL 68 example that are “illegal”. Those characters are definitely in the data being supplied in the data from RC, so they're wrong in the database. This means that fixing is not just a matter of looking at what was supplied; it needs knowledge of how to actually write the code. Thus… ''does anyone know what they should be fixed to?'' If so, please step right in and fix it! –[[User:Dkf|Donal Fellows]] 06:09, 7 September 2010 (UTC)
Anonymous user