Hmm, well, don't be too put off by what happens on the mailing lists; we all like to do our share of bikeshed painting, but a lot of that is just noise. Most of the recent design decisions have actually been simplifications to make implementation easier.
As for threading and events, we've purposefully put that off till we understand how Perl can be properly multi-paradigmatic in that realm. The eventual model is probably going to be something like the unified approach taken in this paper. This being Perl, we will not tell people that they're using a thread continuation monad, because that would be scary. Something like "thread control objects" sounds much friendlier. Perl is all about letting people think they know what's going on until they really need to know what's going on. :-)
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.