That's fine, as long as everyone knows what a barn is, and how to build one. That's not what we have: we have a bunch of people trying to build "a language", from specs that are full of "perhaps" and "maybe".
If you don't even know what a barn is, then you probably don't want to contribute. If you do know, and want to contribute, but don't know how to build one, then you can join the other volounteers and ask for directions.
I suppose that you know at least how to drive in a nail. If you're willing to, then you will be given a hammer and a bunch of nails, and asked to drive them in. Part of Perl 6 development can be like that: read some synopses and write test for pugs. Or post relevant comments if you find inconsistencies, for example.
-
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.
|
