Hi gurus,

I am new to program. I've download parrot source code for study. But on the first glance, I'm a little confused at parrot's layout:
2008-03-25 11:03 <DIR> . 2008-03-25 11:03 <DIR> .. 2008-03-21 09:40 <DIR> apps 2008-03-21 09:44 271,818 ChangeLog 2008-03-21 09:41 <DIR> compilers 2008-03-21 09:41 <DIR> config 2008-03-21 09:44 7,980 Configure.pl 2008-03-21 09:44 13,353 CREDITS 2008-03-21 09:44 4,474 DEPRECATED.pod 2008-03-21 09:44 466 DEVELOPING 2008-03-21 09:40 <DIR> docs 2008-03-21 09:44 683 DONORS.pod 2008-03-21 09:40 <DIR> editor 2008-03-21 09:44 <DIR> examples 2008-03-21 09:40 <DIR> ext 2008-03-21 09:40 <DIR> include 2008-03-21 09:43 <DIR> languages 2008-03-21 09:40 <DIR> lib 2008-03-21 09:44 9,103 LICENSE 2008-03-21 09:44 828 Makefile.PL 2008-03-21 09:44 246,664 MANIFEST 2008-03-21 09:44 17,491 MANIFEST.generated 2008-03-21 09:44 58,896 MANIFEST.SKIP 2008-03-21 09:44 1,001 META.yml 2008-03-21 09:44 35,181 NEWS 2008-03-21 09:44 1,510 parrot-config 2008-03-21 09:44 5,275 parrot.spec 2008-03-21 09:44 22,118 parrotbug 2008-03-21 09:44 4,710 PBC_COMPAT 2008-03-21 09:44 4,785 PLATFORMS 2008-03-21 09:40 <DIR> ports 2008-03-21 09:44 5,013 README 2008-03-21 09:44 1,701 README_cygwin.pod 2008-03-21 09:44 7,447 README_win32.pod 2008-03-21 09:44 3,041 RESPONSIBLE_PARTIES 2008-03-21 09:38 <DIR> runtime 2008-03-21 09:40 <DIR> src 2008-03-21 09:41 <DIR> t 2008-03-21 13:55 32 test.c 2008-03-21 13:55 93 test.cco 2008-03-21 09:44 638 TODO 2008-03-21 09:40 <DIR> tools 2008-03-21 09:44 7 VERSION
It seems to me that there is no any books to introduce how and why organize files.
To understand the meaning of every dir and files took me about 3 to 5 hours. But now, my question is:
is it a typical layout in Linux program? I mean, If I'd like to start a project in Linux, should I create a similar layout?
And If really so, is there a free tool to prompt this process?

Thanks in advance! Any reply would be appreciated!

In reply to Is there a typical layout in linux program? by Anonymous Monk

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



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.