Re: synopsis-changes mailing list

On Sun, 2004-08-01 at 14:17, Stefan Seefeld wrote:
> Hi Gilles,
> 
> Gilles J. Seguin wrote:
> > On Fri, 2004-07-30 at 22:09, Stefan Seefeld wrote:
> > 
> >>Thanks. In fact, I'm working on the C++ parser right now,
> >>to be able to expose a much more rich AST to python to allow
> >>real code inspection and following that code generation.
> >>Drop in if you have ideas or even want to help :-)

> > The main point of this email, how can I see the work that
> > you are doing on the C++ parser.
> > I have done 'svn checkout', so I have revision 1332.
> 
> I'm just starting my work on the backend. My plans are
> (in that order):
> 
> * rewrite some low level classes (Buffer, Lexer, basically)

from what I have seen with CVSweb, it is a major rewrite.

The change to repository, are they supposed to be sent to the
mailing list [email protected] .

Can someone confirm receiving changes from revision 1333 and up.

> * make the existing API more clean (const-correct, more typed,
>   etc.)
> 
> * try to understand how the Parser needs to be changed in order to
>    correctly understand the tokens, i.e. build a correct
>    parse tree / AST (see recent posts on the opencxx list).
> 
> * build a true high-level AST API on top (no more Car() / Cdr()
>   calls !)
> 
> * export that AST API publicly through C++ as well as python
> 
> * get rid of the occ executable, provide a python script instead
>   (for backward compatibility only)
> 
> * solidify the C++ / python APIs to let users build their
>   domain-specific applications either as python scripts or
>   C++ programs
> 
> I realize this is a lot of work. I'm not sure what the timeframe is
> to get all of this done. I'v almost finished the first point
> (the Buffer is committed, the Lexer will follow one of these days).
> If you are interested in getting involved, let me know.