On Fri, Oct 04, 2002 at 12:42:52PM -0400, Erik Lechak wrote:
>
> Is there a document out there that describes the genclass.pl script,
> Vtable.pm and how pmc files become C files?
classes/pmc2c.pl has documentation for the last.
perldoc -F classes/pmc2c.pl
> If I wanted to write a section o
Sean O' Rourke wrote
>On Fri, 4 Oct 2002, Tanton Gibbs wrote:
>> I agree with this; however, I also think it would be nice to have it all in
>> one place. It's a nuisance to have to open every file just to see what it
>> is. By the time I figure out what the 60th file does, I've forgotten what
>
I had a response all typed up, but I erased it. I just want to learn
enough so I can start coding, and these pod conversations are just
getting in my way, and I don't want to waste the Parrot communities time
or bandwidth with my trivial issues. Your time is much more valuable
getting perl6
Erik Lechak wrote:
> ... I decided not to continue on
> the "comment the code route" because I don't like POD. And I think a
> good demonstration of why I don't like it is the ops files. I am trying
> to think of a polite way to introduce java and python people to the ops
> files when they
Erik Lechak wrote:
> I am also trying to document the various structs and their interactions.
> Can anyone out there give a brief description of following:
> Arena
> Memory_Pool
> Buffer
> Memory_Block
> Small_Object_Pool
> Small_Object_Arena
I did announce to write a document on
On Fri, Oct 04, 2002 at 01:35:15PM -0400, Erik Lechak wrote:
> If parrot decides to go the route of embedding documents in its C code.
> Please do not use POD! Find a C developer sitting next to you that does
> not know POD and ask them how they like the flow of the ops files.
> Someone suggest
Tanton Gibbs wrote:
>I agree with this; however, I also think it would be nice to have it all in
>one place. It's a nuisance to have to open every file just to see what it
>is. By the time I figure out what the 60th file does, I've forgotten what
>the first does. It would be nice to have the i
Erik Lechak:
# mark sparshatt wrote:
# I am also trying to document the various structs and their
# interactions.
#Buffer
Unfortunately, I'm not a GC person, so this is the only one I recognize.
A Buffer is essentially a handle on a chunk of memory; it stores a
pointer to the memory, the si
mark sparshatt wrote:
>Hi all,
>
>In another thread Erik Lechak speculated about the possibility of a getting
>started guide. This got me thinking that one of the problems I'd found
>starting out was the number of files that Make up the Parrot system and
>trying to work out what each of them d
On Fri, 4 Oct 2002, Tanton Gibbs wrote:
> I agree with this; however, I also think it would be nice to have it all in
> one place. It's a nuisance to have to open every file just to see what it
> is. By the time I figure out what the 60th file does, I've forgotten what
> the first does. It wou
ot; <[EMAIL PROTECTED]>
Sent: Friday, October 04, 2002 11:17 AM
Subject: Re: Parrot file list
> On Fri, 4 Oct 2002, mark sparshatt wrote:
> > Basically I'd like to know if there's any sort of listing that gives a
> > general description of what each file is used
On Fri, 4 Oct 2002, mark sparshatt wrote:
> Basically I'd like to know if there's any sort of listing that gives a
> general description of what each file is used for.
>
> If there isn't, I've started making some notes of my own and if anyone else
> thinks this would be useful then I can type them
Hi all,
In another thread Erik Lechak speculated about the possibility of a getting
started guide. This got me thinking that one of the problems I'd found
starting out was the number of files that Make up the Parrot system and
trying to work out what each of them does.
Basically I'd like to k
13 matches
Mail list logo
