adrianh,
- Time
I also have no time and yet I find myself porting small pieces of p5 code to p6 just to see how to do it. Since I am not yet taking advantage of the new features, it really is quite straight forward and doesn't take a significant amount of time.
- Reference Material
Have you seen Perl6::Bible? It should help a bit as a reference guide when things are unclear. I know the hassle of joining p6.l to try and get a single question answered so if it isn't in the "book" yet, you might consider joining #perl6 on IRC. Just have a window open lurking and if you have a question, ask and it will be answered or someone will go find the answer for you.
- P6 Rules/OO
Well, as much of PGE (rules) that exists to date from pmichaud is available to Pugs and p5 regexen via PCRE are also available. While full OO support isn't in yet, a great deal is. And when you find something missing that you want - ask for it (really). Having a real need for something is usually motivation enough for the people with time to implement it.
See Get Involved With Pugs for more information. Oh, by the way - Pugs can use CPAN modules now!!
-
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.
|
