On Wed, 11 May 2011, SF Markus Elfring wrote: > > Who needs consensus? > > I guess that a bit of acceptance will be established before a new software > component would be integrated into your tools, won't it? > > > > Just use something that works. > > I assume that a bit more clarification is needed to match "working" features > with expectations. > > > > Write code!!! > > I would like to avoid another reinvention of a coding wheel. ;-) > It would be nice to reuse a thread pool (concurrency features) if an > acceptable > OCaml implementation exists already. > > Examples: > http://raevnos.pennmush.org/code/ethread/doc/Pool.html > http://functional-orbitz.blogspot.com/2011/04/jc-efficient-parallel-programming-in.html
For what it is worth, I don't have any opinion about the various extensions of ocaml to permit concurrency. Simply dividing the files among the available processors is not perfect, but has been good enough for me in practice. Presumably, in a good implementation to provide more fine-grained concurrency, the means of providing the concurrency would be isolated from the rest. julia _______________________________________________ Cocci mailing list [email protected] http://lists.diku.dk/mailman/listinfo/cocci (Web access from inside DIKUs LAN only)
