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

[Steve Meier <smeier-at-NOSPAMalchemyresearch_dot_com>]

Uhm, this isn't ment to be a translator it is ment to be a netlist
manipulator. Translation is a bonus.

I build tools that I need to get something done.

Hence the imputous to backnet was to be able to generate a netlist for a
project that has 28 pages of schematics. Some the of the pages get used
multiple times and this includes the useage of hierarchical buses.

At layout time, as expected, efficient trace routing required swapping
io pins thus causing the actual netlist to not reflect the schematic
netlist. Then we discovered a few schematic issues which required
regenerating the netlist. At this time I can't import the layout program
eco files back into the schematic so I decided to use it to directly
update the schematic.

Hence, the middle scheme routine in backnet.

For the record backnet and my netlister both have very few lines code.
The vast majority of the code is in my version of libgeda.

Steve M.

On Thu, 2007-05-31 at 20:56 -0400, al davis wrote:
> 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



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