Pathologically Eclectic Rubbish Lister | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
BrowserUk,
I would like to point you to a google groups message but apparently the parrot-porters alias to perl6.internals is not getting archived. In any case, Allison just posted the following to the list: I've finished a first pass through PDD 25 on threading/concurrency. It's largely a collection of prior thinking on the subject. Before I start kicking it into a more structured form, I'd like to do an initial round of discussion. This is your chance to mention anything you hoped or expected from Parrot's concurrency models. How do you plan to use concurrency, and in what contexts? What's your favorite concurrency model and why should we consider using it? How integral a role should the new STM play in Parrot's concurrency? Etc. I've changed the name of the PDD from "Threads" to "Concurrency" because: a) the notion of "threads" seems to have taken on mythical proportions, so this is a symbolic step toward practicality, and b) Parrot has more than one concurrency model, and this PDD will be the overview of all them, plus the ways the various models interact. I intend to point her to this thread in case she does not already know about it.Cheers - L~R In reply to Re: Parrot, threads & fears for the future.
by Limbic~Region
|
|