Re: [ng-spice-devel] Requirements for frontend/backend


To ng-spice-devel@ieee.ing.uniroma1.it
From Steve Hamm <Steve.Hamm@motorola.com>
Date Mon, 20 Nov 2000 15:41:46 -0600 (CST)
Cc ng-spice-frontends@ieee.ing.uniroma1.it
Delivered-To mailing list ng-spice-devel@ieee.ing.uniroma1.it
In-Reply-To <20001120221952.B32529@cgmd80028.chello.nl >
Mailing-List contact ng-spice-devel-help@ieee.ing.uniroma1.it; run by ezmlm
References <00111722530800.00661@localhost.localdomain><20001119224846.A26364@cgmd80028.chello.nl ><0011192231330C.21525@hobbes ><20001120221952.B32529@cgmd80028.chello.nl >
Reply-To ng-spice-devel@ieee.ing.uniroma1.it

---"Arno" == Arno W Peters <a.w.peters@ieee.org> writes:

Arno> I would argue that netlist parsing should also be done in the
Arno> frontend.

This would make parsing happen through an interpreted frontend?
Probably not a good idea. Once a netlist language has been enhanced to
allow component values to be expressions involving parameters which
can be passed through the subcircuit hierarchy, the complexity of
parsing goes up rather dramatically. Then, on top of this, people are
extracting parasitics using not terribly smart extractors, which can
balloon a netlist from under a megabyte to 7 or 8MB easily. Unless the 
language is much more regular than a SPICE netlist, it can be slow
going...

--Steve




Partial thread listing: