gEDA-dev: Broken slotting

Peter Clifton pcjc2 at cam.ac.uk
Wed Sep 12 06:47:02 EDT 2007


On Wed, 2007-09-12 at 06:43 -0400, Stuart Brorson wrote:
> Another way to solve the problem is to have a gnetlist function
> "get-net-attribute-by-pinseq-and-slot(component, pinseq, slot_no)".
> This function didn't exist when I wrote the other stuff, and using
> pinseq modulo slot number to get the net attributes seemed like an
> easy way to get it done.
> 
> Ummm, I guess my only question is: Why is it bad to pass around a
> pinseq larger than the number of pins on the first slot?   Maybe I
> need to read through this whole thread again.....
> 
> Stuart

Its not just passing around though.. the code actually re-writes the
pinseq attribute on the slotted components in libgeda / gschem's
data-structures. That is breaking the use of pinseq to index the
device's pins (for pinnumber= updates when altering slotting).

Peter




More information about the geda-dev mailing list