Re: class library design selection

> 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.

This argument is unclear for me.


> That is for information exchange between developer.
>   

Can we improve the exchange on design decisions?


> 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.

Do you want to stick to such low API levels?

Regards,
Markus