To that end I've been exploring the source tree.
As a newbie, I've got a lot of questions, So I'm attempting to learn by
updating and adding documenation.
My patches may seem obvious to the seasoned pugs hacker, however, I'm
attempting to help newbies be able to understand more of the
directory structure and architecture without a personal tutorial.
I'm sure I've got some things wrong, I've figured out what I know by
just poking around.
Anyway, this is my first attempt at a pugs doc patch :)
Speaking about directory structure how about
/runtime or prelude (What exactly is a prelude?
how does it differ from a runtime library?)
I found pugs/perl5/ a little confusing at first
> Anyway, this is my first attempt at a pugs doc patch :)
> Comments welcome!
Welcome. I'm sure someone will offer you a commit bit very soon. In
the meantime, my only comment is that, outside of class, module, file,
and package names, where spaces are too significant, Perl 5 and Perl 6
should have a space between the word and the number.
It's a little thing.
On Aug 19, 2005, at 10:15 AM, Kevin Tew wrote:
> I've been watching pugs for a while and would like to get more
> To that end I've been exploring the source tree.
> As a newbie, I've got a lot of questions, So I'm attempting to
> learn by
> updating and adding documenation.
> I'm sure I've got some things wrong, I've figured out what I know by
> just poking around.
So has mostly everyone else :)
> I found pugs/perl5/ a little confusing at first
That directory has turned into a bit of a catch-all for all the non-
backend stuff. I would like to see pugs/backends/your_backend_here/
think I've heard autrijus mention something similar, but it's been
low on the list of priorities.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
-----END PGP SIGNATURE-----