Talk:Indeterminacy in concurrent computation: Difference between revisions

Content deleted Content added
nonsense: new section
Sense and nonsense: The physical indeterminacy of hardware used in the implementation of concurrent programming languages results in indeterminacy in the behavior of programs.
Line 143:
:The line actually reads as follows: "Indeterminacy in concurrent computation is concerned with the effects of [[indeterminacy]] in [[concurrent computation]]." where the links provide additional meaning. But you are right that we should word it better.[[Special:Contributions/67.169.49.29|67.169.49.29]] ([[User talk:67.169.49.29|talk]]) 14:45, 2 June 2009 (UTC)
 
== Sense and nonsense ==
 
I'm sorry to be frank, but this section is nonsensical:
Line 157:
 
(Also, please note that many languages has been formalized with some 'logic', even the ones that does not favor the 'logic programming' paradigm) --[[Special:Contributions/187.40.172.119|187.40.172.119]] ([[User talk:187.40.172.119|talk]]) 03:25, 20 August 2010 (UTC)
 
The hard part is formalizing concurrency. The formalization of [http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.40.954 ISO Prolog] does not have any concurency. The physical indeterminacy of hardware used in the implementation of concurrent programming languages results in indeterminacy in the behavior of programs. It is well known that concurent programs cannot be reduced to pure logic (see [http://arxiv.org/abs/0812.4852 Common sense for concurrency and inconsistency tolerance using Direct Logic(TM) and the Actor Model]). [[Special:Contributions/64.134.238.26|64.134.238.26]] ([[User talk:64.134.238.26|talk]]) 20:54, 20 August 2010 (UTC)