New Source Structure


To ng-spice@ieee.ing.uniroma1.it
From Paolo Nenzi <pnenzi@ieee.ing.uniroma1.it>
Date Wed, 11 Aug 1999 18:20:15 +0200 (CEST)
Delivered-To mailing list ng-spice@ieee.ing.uniroma1.it
Mailing-List contact ng-spice-help@ieee.ing.uniroma1.it; run by ezmlm
Reply-To ng-spice@ieee.ing.uniroma1.it

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. 

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 ?

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 ?


Partial thread listing: