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. :-)
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
