Re: class library design selection

On Tue, 2007-05-22 at 13:00 +0200, Markus Elfring wrote:
> > 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.
> >   
> 
> Both are necessary data formats. They have got different powers.

Nah, i see no necessity there.
If language chosen for source is the Boost Spirit parser
ebnf is merely a pale representation of the real thing.

And class diagram one of the many graphical representation
of documentation representation that is done generally at the 
or not at all. That is for information exchange between
developer.

> > So source transformation need an API.
> 
> Do you want to achieve consensus on further API extensions?

For source transformation the grammar is the API, for C++ that
is the current "ptree".
You need to provide modifications to the grammar, and here we stick
to standard, means any ideas to have change there are born dead.