On Feb 1, 2008 9:49 PM, Will Coleda <[EMAIL PROTECTED]> wrote:
> On Feb 1, 2008 3:24 PM, Klaas-Jan Stol <[EMAIL PROTECTED]> wrote:
> > hi,
> >
> > for people starting to use PAST nodes, it might be difficult to get
> started,
> > or not very clear what you can do with it. For instance, suppose you
> have a
> > certain language construct to translate, you need to figure out which
> past
> > nodes you have to create, and what attributes.
> >
> > would it be an idea to create a document describing the PAST nodes by
> > example, showing what the attributes do (what effect) and how the
> generated
> > PIR is affected by the several options?
> >
> > an example is attached.
>
> +1
>
> > If this isn't considered worhtwhile,I won't work on it any longer (I
> > actually do have other stuff to do :-),
> > but if this idea is thought to be a good idea, i'll work on it a bit
> more.
> > Other people are invited to add stuff too :-)
>
> Improving the state of the documentation is always welcome; think if
> it as an investment to get even more people working on stuff.
Ok, I did some more writing and added the file to docs/, named
"past_building_blocks.pod".
The name can be changed later if necessary.
I also intend to add more "tips&tricks", common constructs that can be used
to write efficient and easy action methods.
I invite all PCT users (rakudo hackers :-) to add their tricks if they know
of "good practices".
I'm also thinking of something similar to compiler_faq.pod, which is an
index of "how do I implement X in PIR?". Similarly, there could be some kind
of index for "what PAST nodes do I need to implement a {"if", "while",
"assignment", "for"}-statement".
kjs
