X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; bh=2jer1lfn+6rwOeksTZ3R2YC+WLUTeAlUYMEvVKEL6uE=; b=XXlqwvi8N7dIMd1fAP3eCYVnVU9yGS3a749qxY01g7xG7fpo991a0bqRSCtzyc0qo5 jVt6Qytdr7z2XX2Q1Qe0gcE8ERPvA3/8tjP8nZk0sQr/CYkZocJWJ+l3s99syHd4apnK IdKpXlJlLyPHgP7oxKjYfzJH1JPO+Xat00/N9gBOVaz05/h+ay6XmrBCSTFTmxQ8iAb3 YKsPEtUyBz8UIuZSKyU0+gXpccRwHFmg2r58n0XZTKu7/qMqdRRadtG4dKzrc0eBPUEO wVJRHWC0ZI1/blL0VY8Iroq2XLxi6EetvjTBxDXGAMJoRCKP+GvjhrX0ceyoMdb9w6wB Y4Qw== X-Received: by 10.112.35.138 with SMTP id h10mr17006267lbj.6.1451758224281; Sat, 02 Jan 2016 10:10:24 -0800 (PST) Date: Sat, 2 Jan 2016 19:10:18 +0100 From: "Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com]" To: geda-user AT delorie DOT com Subject: Re: [geda-user] ideas on slotting and mechanisms for grouping/associating heterogenous symbols. Message-Id: <20160102191018.5e68c0c4ecc70a49bd9998f6@gmail.com> In-Reply-To: <201601021755.u02HtOWs020325@envy.delorie.com> References: <8444F816-17CE-4A56-A982-4A60DEDA72B8 AT noqsi DOT com> <87FC7D4C-157A-499E-8B93-97653D6A7C68 AT noqsi DOT com> <624E6A69-62CE-4FCB-9D44-9FDF036254A3 AT sbcglobal DOT net> <56880043 DOT 7040003 AT ecosensory DOT com> <20160102182739 DOT 5d195829880cf75768ae0a82 AT gmail DOT com> <201601021755 DOT u02HtOWs020325 AT envy DOT delorie DOT com> X-Mailer: Sylpheed 3.5.0beta1 (GTK+ 2.24.25; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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 > > I agree, refdes is good choice. > > Note that giving refdes this special meaning, means that gate swapping > (or sharing, across heirarchy instances) between packages is no longer > an option. Is that a reasonable compromise? That's a collision. Ideally all symbols ending up in the same footprint should have the same refdes. I would say the naming scheme for hierarchy does not fit for this case and I can't figure out how to get a good solution. Nicklas Karlsson