Re: [ng-spice] Pizza Code


To ng-spice@ieee.ing.uniroma1.it
From Manu Rouat <emmanuel.rouat@wanadoo.fr>
Date Mon, 26 Jul 1999 20:51:20 +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.990726200714.27887A-100000@ieee.ing.uniroma1.it >
Reply-To ng-spice@ieee.ing.uniroma1.it
Sender rouat@war.wanadoo.com

Paolo Nenzi wrote:
> 
> Dear Manu,
> 
> I am compiling your version of spice3f5-pizza and I see the situztion you
> were complaining: spice code is a mess, there are a lot of warnings, even
> in the analysis code.

yep :-)

> 
> I will ask the permission for installing a CVS on the server (I have got
> an idea of what it is)
> 
> I would like to ask you:
> 
> 1) Should we make new code in parallel to the debugging process ? I mean,
> write new code for the part already cleaned in parallel to the debugging
> of other parts.
> 4) We should start fixing compiler warnings and then memory leaks or
> proceed in parallel ?

I would start with cleaning, and then the debugging part can go in
parallel with adding/modifying code.

> 
> 2) Should we port it to ANSI C avoiding the huge number of #ifdef ? I
> think that an ansi compliant compiler can now be found everywere. We can
> change the function declaration to theFunction (char * toto, ...)

Yes - sooner or later, I will add a '-ansi' tag to gcc.


Ansi is preferable, most compilers are ansi nowadays.


manu



Partial thread listing: