Re: class library design selection

On Sun, 2007-05-20 at 22:00 +0200, Markus Elfring wrote:
> > Both are C++ front end and are tools used by/for Synopsis.
> > No infrastructure there.
> >   
> 
> How much can we learn from the differences in these approaches about 
> required classes for higher levels on language processing?

That different tools must be used depending on what you want to do.
- opencxx allows source transformation using the "ptree".
- opencxx allows automated source transformation. Which is also
  adding source codes that permit adding reflection.
  But the template part is incomplete and license problem :-(
Synopsis want that feature also, that is why we have "ptree".
We know that "ptree" reflect the grammar, isomorphism.
We know that class diagrams is a less powerful representation than
ebnf(extended Backus-Noor Form)(check syntax last acronym, may
be wrong), ie class diagram loose evaluation order.
So source transformation need an API.

We know that all present projects used an intermediate language
representation(IL) for other kind of analysis. That include
optimization, and inter language framework. Synopsis has the
AST module. So another API.

> > Do not remember now what it is
[...]
> Can anything be reused from the CppInfo API for Synopsis' purposes?
> http://g4re.sourceforge.net/GXL/

Make the thing work on GCC version 4.x.
We have learn from there, that analysis require massive amount of
data.  Mozilla is around 15GB.  Means, tools "must" be able to
process data not in memory, at least in my case :-(

Stefan does it make sense to used it.
Does it make sense to upgrade the thing to version 4.1 of GCC.

> > Synopsis and Ductape are on the same track
>
> I do not see that they have got much in common from the OpenC++ sources 
> so far. Why are other designs not "on track"?

Primary concern is getting information for further analysis or
automatization. 

> > Some ideas can be borrow from there
> > http://www.mono-project.com/ECMA
> 
> How much do you want to add to the Synopsis class library from this 
> specification?

Synopsis will require a parser for C#, we are probably in need of
more details to have that AST.