Re: Re: software design clarification

> You seem to keep arguing for a design that needs to be done, but you fail
> to tell us what it actually is that you want to design. Think "use-case driven
> design", if that helps.
>   

Example: How would you perform a search for called functions with 
non-void return types in the source files?


> common to what ?

Do Python and C++ use the same Synopsis class library implementations?


> And why the future tense ? What about the existing APIs ?
>   

Your own documentation indicates this.
http://synopsis.fresco.org/docs/DevGuide/type-analysis.html


> No idea. To be honest, such a name change is the least of my concerns right now.
>   

I expect consistent names as preconditions for correct design.
Are more software developers interested in a proper source code refactoring?


> OK, fine. That paragraph suggests swig does some code analysis, too.
> What was your question, then ?
>   

I guess that it will need some more efforts for Synopsis souce code to 
achieve similar parsing capabilities like SWIG or AspectC++.

Regards,
Markus