Beefy Boxes and Bandwidth Generously Provided by pair Networks
There's more than one way to do things

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
I think that you should invest some time in documentation of the project it self, what will be much more easier to integrate new developers to the development of Parrot (in any area of the project, not only the VM or Perl6).

Today if someone get the Parrot source it doesn't know what does what, and how to work in something that it want to add or fix, and bingo, you lost some potential developer. If understand the project be a intuitive thing, we can work faster in the exactly point that we need.

For example, get the Perl5 sources, we have a lot of .c files, directories, libraries, specific OS versions, etc... But we doesn't have a main document that exaplain what is what in the source tree! Will be much more interesting to have in the top of each .c file of the Perl CORE, some text that says, this files is for bla bla bla. We also should have some list of the pourpose of each directory of the distribution, like know that ./ext are the modules that need to be compiled, and ./jpl is just a sub project that integrates Perl and Java, etc...

For who knows Perl and hack it this is silly, we think that is easy to "hack" and look all the sources. Well, for someone that work with Perl for years, yes, is silly. But let's say that you got Perl today, for the 1st time, and want to add/change/play with the sources? A good documentation will be good, and this is what we need to do with Parrot, be able to play easier with it just from the 1st time.

Graciliano M. P.
"Creativity is the expression of the liberty".

In reply to Re: Time to change the (Perl 6) guard! by gmpassos
in thread Time to change the (Perl 6) guard! by Elian

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • 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 or How to display code and escape characters are good places to start.
Log In?

What's my password?
Create A New User
Domain Nodelet?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others having an uproarious good time at the Monastery: (4)
As of 2021-08-04 08:59 GMT
Find Nodes?
    Voting Booth?
    My primary motivation for participating at PerlMonks is: (Choices in context)

    Results (41 votes). Check out past polls.