X-Authentication-Warning:	delorie.com: mail set sender to geda-help-bounces using -f
X-Recipient:	geda-help AT delorie DOT com
X-Original-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=gmail.com; s=20161025;
	h=date:from:to:subject:message-id:mail-followup-to:references
	:mime-version:content-disposition:in-reply-to:user-agent;
	bh=v5C0Q1OMYW/3DH7YiBdE+oux7PNuN/eDI1hok42BaWA=;
	b=gn1zMMdgIMSAgOKki6pDs0mbiPau7RtialhWg6FSL8uOG0y6e3zvvrcyH+KzKMY9mE
	emLxr9BHEiBo5rMS8YJtFxH8yJKj6qh34CcgW6Ez7uvKU06w9PhGr7tq/ZAe58viiSbU
	TQnJGG/CKXF9wgwhlx+/vj9X6l1G5++iM+q9D2xosV5gdp04QoTQAIgF6HWEzR7bKUUp
	bkARKszwos0eoB0NRhyxWSrWOYKNSEAHtC6/U6hO0oIrmelKjXX3br5MfDvnoTzDuHrT
	JP0a4W9QcATLAxjMkpi9aV2MKu8LRFCQe/Hp1OV9HP7RkwSdHMtDaXznphyywTBaFzqa
	el1A==
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:date:from:to:subject:message-id:mail-followup-to
	:references:mime-version:content-disposition:in-reply-to:user-agent;
	bh=v5C0Q1OMYW/3DH7YiBdE+oux7PNuN/eDI1hok42BaWA=;
	b=cy1kY/qKjRXbPPSG7MIec42Z+2QnXEgoXErNH2Sh9Va6MUS29Y8fb+4qfHroWBHzVq
	IabOCoW6B4GR9OQkj0F+Ei31ZfC4WdZ7sVK8Sk7VbXJBWYUrDxlNAh0Wx1dBe4cNbZHr
	D/wEredfo8/GkxjQLVaS1VUan4P6EIQ/RryNtlc/ngsR/1LIQLII45qzs2GSuBnS0f7Y
	TF8hSZhBMYm3GdIPDbQp7ry2eJglpapa7Z8CLUuyf29RXTCppqH4KPeDSHAINJ3EU6/t
	XVJALQK7A0s2TStTuA4drzw5CeCbcR9mFvrUYxcT8hovZvJeVpWPLXUe54Rv44ijVxij
	VsVg==
X-Gm-Message-State:	AMke39knbSak7r0ezR41EXXkr/NTXOs1PPI1fetRz5NvjFB8hGfI2s6icEgUDDYGNM7bmg==
X-Received:	by 10.25.89.148 with SMTP id n142mr3447708lfb.64.1487453009902;
	Sat, 18 Feb 2017 13:23:29 -0800 (PST)
Date:	Sun, 19 Feb 2017 00:23:27 +0300
From:	"Vladimir Zhbanov (vzhbanov AT gmail DOT com) [via geda-help AT delorie DOT com]" <geda-help AT delorie DOT com>
To:	geda-help AT delorie DOT com
Subject:	Re: [geda-help] Please help with multiple-pages schematics
Message-ID:	<20170218212327.GA17868@localhost.localdomain>
Mail-Followup-To:	geda-help AT delorie DOT com
References:	<FE10A69B-DB86-4182-A223-25AEE5FF697E AT noqsi DOT com>
	<CAEoZ9HgxR8qm9vfr6TUHgxPTeOGZ=a7Mc8NrwmPvJOLyXHa5fg AT mail DOT gmail DOT com>
	<CAJXU7q8-XPJ+9k3C4bVWvYe5ci1eFGrnNfeCBQoykhdWAM9s0g AT mail DOT gmail DOT com>
	<11BDEC14-5D1D-4157-B552-582C1E75D00E AT noqsi DOT com>
	<20170218180232 DOT GB23464 AT localhost DOT localdomain>
	<4FA4C5C8-4B56-493A-94AC-1D4920C201F3 AT noqsi DOT com>
	<20170218185614 DOT GA25608 AT localhost DOT localdomain>
	<FAF62B87-D375-416A-A008-77E9E33294C4 AT noqsi DOT com>
	<20170218202533 DOT GA6290 AT localhost DOT localdomain>
	<20170218205206 DOT 5825C812BA6B AT turkos DOT aspodata DOT se>
MIME-Version:	1.0
In-Reply-To:	<20170218205206.5825C812BA6B@turkos.aspodata.se>
User-Agent:	Mutt/1.5.23 (2014-03-12)
Reply-To:	geda-help AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	geda-help AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Sat, Feb 18, 2017 at 09:52:06PM +0100, karl AT aspodata DOT se wrote:
> Vladimir:
> ...
> > though IMO the same pin must never appear in multiple places. Never!
> ...
> 
> I don't see why not, as long as you don't connect the pin in more than 
> one of thoose places. If you have a ban on same pins in multiple places
> you'll have more work generating symbols for devices with high pin 
> count.

Karl,

I'm just saying having same pins in various places in schematic
for one component is misleading. And I would want to avoid such
usage. I agree it could lower work on symbols in some cases,
though I don't consider it a good practice.

-- 
  Vladimir

- Raw text -