Re: Synopsis - tutorials

On 4/26/07, Stefan Seefeld <[email protected]> wrote:
>
> Roman Yakovenko wrote:
>
> > Thanks. I built the documentation and I am reading it now. One more
> > question what tree I need to travel, in order to extract all
> > declarations: ast or parse tree?
>
> That's a good question, and answering it requires more context.
> My goal is to make the parse tree (as well as related representations,
> such as a symbol table, type repository, etc.) ready to become a public
> API. However, I'm not there yet, i.e. it still keeps evolving.


The question is how much? If you make small not backward computable changes,
I think I can live with them

The parse tree is translated into an 'AST' (a pure python representation),
> which is stable and used in different contexts. Thus, you may look at
> that first. However, depending on your needs you may find that it doesn't
> provide enough informmation for your purpose (code generation). In that
> case, we either need to fill the holes by adding more attributes to the
> AST,
> or try to get the parse tree into a state which is usable by you (and
> others).


I  am not sure I see the difference between both trees. What tree provide
high level description of declarations?

I do have some (experimental) code to expose the parse tree (etc.) to
> python using boost.python, and so I very much welcome any additional
> motivation to move further in that direction.
>
> Any help would be highly appreciated.


I think I can help you with exposing the code to Python, just describe what
still should be done.

-- 
Roman Yakovenko
C++ Python language binding
http://www.language-binding.net/

_______________________________________________
Synopsis-devel mailing list
[email protected]
http://lists.fresco.org/cgi-bin/listinfo/synopsis-devel