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

[al davis <ad136-at-NOSPAMfreeelectron_dot_net>]

On Thursday 31 May 2007, Steve Meier wrote:
> 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.

I think you are trying to do too much.

Do not try to guess what optimizations anything might want.

I think what John is saying is that he does "hierarchy" by 
multiple schematics, in separate files.  The translator would 
produce one output file for each input, and he uses "make" to 
manage it.  It's a good way to do it.

So, for a translator, just translate the one input file to one 
output file, and let something else manage the other details.  
Try to preserve as much data as you can in the translation.  
Don't try to add information that is not there in the input.


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