X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com Date: Wed, 26 Aug 2015 18:58:06 +0200 (CEST) From: Roland Lutz To: geda-user AT delorie DOT com Subject: Re: [geda-user] netlisting libraries In-Reply-To: <6CBA9A3C-526A-4364-9E70-83A910349E14@noqsi.com> Message-ID: References: <20150824223846 DOT 0ba61ba7 AT jive DOT levalinux DOT org> <55DBA2B7 DOT 1080501 AT ecosensory DOT com> <55DC31E0 DOT 9050606 AT jump-ing DOT de> <20150825215611 DOT 1794b153c4160dddb739b6d3 AT gmail DOT com> <55DDCF2E DOT 6070505 AT ecosensory DOT com> <6CBA9A3C-526A-4364-9E70-83A910349E14 AT noqsi DOT com> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="8323329-894062553-1440608287=:6849" Reply-To: geda-user AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: geda-user AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --8323329-894062553-1440608287=:6849 Content-Type: TEXT/PLAIN; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8BIT On Wed, 26 Aug 2015, John Doty wrote: > The overloading of pinseq is really the only one I’ve found troublesome, > so gnet-spice-noqsi gives you other ways to handle slotted devices. I've never understood the motivation for the SPICE netlist backends to use pinseq= at all. Is this just a hack to get the unslotted pinnumber? Or is there some other mechanism involved? (If it's just about the unslotted pinnumber, this is easily solved using the refactored netlister--instead of cpin.number, use cpin.blueprint.get_attribute('pinnumber') which doesn't consider slotting.) Roland --8323329-894062553-1440608287=:6849--