What's concering to me is that if you start with bdf's perl7faq, and you get to the part about Cor, you see the repo is just for ideas on the wiki. It's only then that way down if you're still reading, you may be shocked to see this: Cor is the product of Ovid's deranged mind, but he largely stole a bunch of ideas from Stevan Little, who's working on a prototype. Sawyer X asked great questions and gave a few good ideas to make it even better. If this goes into the core, Sawyer is the person who will likely guide that effort. ... maybe our saving grace is that Damian Conway has worked to pervert the process. Though how perverted this may be remains to be seen.
So call it standard perl rebranded or backdooring Moose into Perl named for a mogrel dog this time, but the more I dig into this the more exclusionary and occluded the process becomes. And don't get me started about some who I've heard of being shadowbanned on p5p - receiving emails yet their emails getting delivered directly to /dev/null.
-
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.
|