Re: Re: software design clarification

> Let's take "abstraction" as a process, starting with concrete use cases,
> and looking for commonalities. So one question becomes: "What programming
> languages can be represented by the Synopsis AST ?".
>   

I'm also interested in this one. - I've tried to suggest a top-down 
design approach while you are asking for a bottom-up design here. I hope 
that we can meet somewhere in the middle.
Can a common class library be achieved that will be implemented in some 
target programming languages?

When are you going to rename parts of your software from "Tree" to 
"Graph"? (I guess that the separation of concerns between "T" and "G" is 
another nasty source of confusion. When is the "S" related to the terms 
"syntax" or "semantic"?)


> AFAIU, swig does quite the opposite from Synopsis. It takes a high-level
> interface description, and generates wrapper code.

Is C/C++ high-level enough for an IDL?   ;-)
http://www.swig.org/Doc1.3/Introduction.html#Introduction_nn10


> IDL is nothing but a language. There are various language bindings that
> define the mapping to language-specific interfaces. So this, too, is a simple
> matter of code generation, not code inspection.
>   

How is the current state for the support of the CORBA interface 
definition language?
http://synopsis.fresco.org/docs/Tutorial/idl-parser.html


> What 'libraries' do you have in mind ? The code implementing a C++ compiler
> frontend surely isn't related to python at all.
>   

Front-/Back-ends can be written in Python and C++.

Regards,
Markus