Re: Re: Synopsis roadmap

David Abrahams wrote:

>>>So, how about it?  It is getting a bit urgent for us to have this
>>>functionality.  If I can help in any way, I'd be willing.

can you quantify that 'urgent' a bit ?

>>Could you (or Doug) please summarize what you expect synopsis to do
>>when it encounters such code ?
> 
> 
> I think Synopsis needs to build AST for it, just like any other code.

[...]

> Absolutely.  Let's break it down.  But I'm not sure how you're drawing
> those distinctions, so I need to hear more from you I think.

The obvious first step is to add an option to the lexer and the parser
to recognize the new tokens and generate appropriate parse tree nodes.

As you pointed out, this doesn't any additional semantic analysis,
and so shouldn't take very long (assuming the parser is able to deal
with the rest of the code, too).

The next step, then, is to extend the AST to support the new entities
and generate those from the extended PTree.

Correct ?

What do you expect to do with the AST ? Given that you could also
access the PTree directly (both, in C++ as well as Python), would
you rather operate on that ?

Thanks,
		Stefan