Re: gEDA-dev: gnetlist as one way path?

[John Doty <jpd-at-NOSPAMwispertel_dot_net>]

On May 31, 2007, at 6:06 PM, Steve Meier wrote:

> Do you now? You build complex net lists out of smaller netlists? and
> only update those that the schematic is younger then the netlist?
>
> backnet could have the capability to do somthing like that but not
> gnetlist. Much like a linker...

In the case where I do this, the deliverable product is a  
hierarchical Spice netlist. To make this, all I need to do is  
concatenate the subcircuit netlists. Not a general solution, though.

>
> The netlister would have to generate an intermediate format whcih not
> only has its own netlist and bus list but also a list of which  
> pages are
> one hierarchy level down. For hierarchical bus support as well as net
> support I use a symbol which associates an internal name with a symbol
> pin. This would have to be retained.
>
> Then backnet could start with the top level intermediate netlist file
> and read in additional intermediate net list files as required.
>
> Then write the desired output netlist format.
>
> With this capability the utility make could be used to check to see
> schematic files need to be processed into the intermediate netlist
> format with the netlister and then build the final netlist with  
> backnet.

Sounds good. Back a decade or so, I used a netlist merging program I  
wrote in AWK to merge a graphical schematic from Viewlogic with a  
database-generated netlist to make a backplane design that was mostly  
connections described by the database, but contained some power  
conditioning filters described by the schematic also. It seems to me  
your approach can lead to a general facility for doing this kind of  
thing. There is no universal representation for designing or  
communicating circuits to human readers: it makes excellent sense to  
design each piece in its natural representation and then merge the  
designs in a common netlist.

Go for it!

John Doty              Noqsi Aerospace, Ltd.
http://www.noqsi.com/
jpd@noqsi.com




_______________________________________________
geda-dev mailing list
geda-dev@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev