Re: [ng-spice] New Source Structure
> If you don'y put it in CVS, how can I do the autoconf interface?
There are so amny changes in the directory structure that Iam wandering
how to commit them to the CVS. Any idea is welcomed.
> My feeling : all .c files (in all directories) should have their own .h file
> (in the same directory)
Me too, but I am thinking to build an "extended API" structure to let
people write code for spice (ala apache) and in this kind of interface
people shouls have access to some includes (probably the most general
ones).
> All functions that are required as external should then be declared as such
> in a generic spice.h files (or devices.h or whatever).
Hmm, I think you have answered my doubt, a single huge API file.
> Also, all usefull macros should be merged into a macros.h file.
What about complex functions macros, they should remain macros or we can
convert them into inline functions ?
> I think that only devices should be modular , not analyses.
OK, you are rightm,it is very difficut that users will need a good
simulator without analyses ;-).
Paolo
Partial thread listing:
- Re: [ng-spice] New Source Structure, (continued)