>(unless we could put a list in the pinnumber attribute, say in this >case pinnumber=3,4,5,6; call it pinlist instead of pinnumber if you >want).
I've seen chips where different packages have different numbers of, say, ground pins. So a one-to-many mapping would be useful. > pinseq=$newpinseq <--- overwritten pinseq for simulation/netlist generation I think we can do this on the fly, no need to store it. My reasoning behind using pinlabel is that it's something that shows up on the screen, so there's an easy way to see what it is. _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
