Re: [ng-spice] New Source Structure


To ng-spice@ieee.ing.uniroma1.it
From Manu Rouat <emmanuel.rouat@wanadoo.fr>
Date Wed, 11 Aug 1999 22:29:13 +0200
Delivered-To mailing list ng-spice@ieee.ing.uniroma1.it
Mailing-List contact ng-spice-help@ieee.ing.uniroma1.it; run by ezmlm
Organization la Guilde
References <Pine.LNX.3.96.990811181220.6201A-100000@ieee.ing.uniroma1.it >
Reply-To ng-spice@ieee.ing.uniroma1.it
Sender rouat@war.wanadoo.com

Paolo Nenzi wrote:
> 
> Hi all,
> 
> In the struggle to get the sources of spice3f5 more readable and
> debuggable, I have extracted all analyses files from the ckt directory,
> creating an src/an/ hierarchy: in the an/ directory there exist one
> directory per analysis (as in the src/dev hierarchy). This change in the
> structure of source code have surely broken the sources, so I have not
> uploaded this new structure to the CVS yet. I will wait for Manu for the
> autoconf/automake interface and in the meantime will continue to clean the
> code.

If you don'y put it in CVS, how can I do the autoconf interface?

> 
> I would like to ask a question about analyses modules structure:
> 
> I am planning to make an <an_name>ext.h file containing externals for all
> the functions defined in the analysis code, should this file be in the
> analysis directory or in the src/include ?

My feeling : all .c files (in all directories) should have their own .h file
(in the same directory)

All functions that are required as external should then be declared as such
in a generic spice.h files (or devices.h or whatever).

Also, all usefull macros should be merged into a macros.h file.

> 
> In the future plans are two distinct shared libraries:
> analysis library and various device libraries: what is the best source
> struture to achieve the necessary modularity ?


I think that only devices should be modular , not analyses. 

manu



Partial thread listing: