Re: gEDA-dev: Broken slotting

[Stuart Brorson <sdb-at-NOSPAMcloud9_dot_net>]

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



On Wed, 12 Sep 2007, John Doty wrote:

>
> On Sep 11, 2007, at 10:52 PM, Ales Hvezda wrote:
>
>>
>> Random question, obviously this slipped by me, but there is code
>> that is
>> changing the pinseq= number on the fly?  That doesn't seem right to
>> me.
>> I always assumed pinseq= would stay constant.
>
> This was Stuart's attempt to make slotted components netlistable for
> Spice. Have a three terminal four slot component with pinseq from 1
> to 3 behave as if it had pinseq from 1 to 12. I personally think that
> this is confusing and not especially useful. For consistency, need a
> spice-slotdef attribute, and maybe a spice-pinnumber attribute would
> be better for unslotted components, too. The way the Spice back ends
> use pinseq has been a frequent source of confusion, even without this
> slotting trick.
>
> 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
>


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