Re: [ng-spice-devel] Three kinds of complex numbers


To ng-spice-devel@ieee.ing.uniroma1.it
From "Arno W. Peters" <a.w.peters@ieee.org>
Date Sat, 17 Jun 2000 17:10:19 +0200
Delivered-To mailing list ng-spice-devel@ieee.ing.uniroma1.it
In-Reply-To <Pine.LNX.3.96.1000617104229.15142C-100000@ieee.ing.uniroma1.it >; from pnenzi@ieee.ing.uniroma1.it on Sat, Jun 17, 2000 at 10:46:21AM +0200
Mailing-List contact ng-spice-devel-help@ieee.ing.uniroma1.it; run by ezmlm
References <20000616235126.C20747@cgmd80028.chello.nl > <Pine.LNX.3.96.1000617104229.15142C-100000@ieee.ing.uniroma1.it >
Reply-To ng-spice-devel@ieee.ing.uniroma1.it
User-Agent Mutt/1.2i

On Sat, Jun 17, 2000 at 10:46:21AM +0200, Paolo Nenzi wrote:
> On Fri, 16 Jun 2000, Arno W. Peters wrote:
> 
> > You will agree with me that only one definition is sufficient and the
> > others should go.  I welcome patches that work toward this goal.
> 
> I agree, one definition constistent throughout the code is sufficient.
> 
> If we are moving towards an GPL'ed ngspice which acts as a library, we
> may insert these definitions in a single top-level include file like
> ngspice.h. We can use a convention like the one used in OpenGL:
> 
> SPreal, SPcomplex, SPdouble, SPvector and so on...

I am all in favour of a single naming convention.

I disagree with the implementation you propose: a single top-level
header file.  I propose to use that top-level header file to include
all necessary other header files to allow compilation against the
ngspice library.  It shouldn't contain a single definition, only other
#include's.

The library and its API are parts of the ngspice project that have not
yet received much attention.  This is because we're still sorting out
the code, trying to construct an API as we progress with the
refactoring.

Regards,
-- 
Arno

PGP signature


Partial thread listing: