X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
Date: Mon, 31 Aug 2015 13:06:13 -0400
Message-Id: <201508311706.t7VH6D4t019776@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: geda-user AT delorie DOT com
In-reply-to: <alpine.DEB.2.00.1508311141070.6924@igor2priv>
	(gedau AT igor2 DOT repo DOT hu)
Subject: Re: [geda-user] back annotation proposal (RFC)
References: <alpine DOT DEB DOT 2 DOT 00 DOT 1508301838470 DOT 6924 AT igor2priv> <201508301802 DOT t7UI2twS031311 AT envy DOT delorie DOT com> <CAM2RGhRgPQG2WDFVb0SFvMbypyYKS2oYtD=851WHR6fOB4iWdA AT mail DOT gmail DOT com> <201508310341 DOT t7V3fcfh022966 AT envy DOT delorie DOT com>
 <20150831111604 DOT 5b1bb421bc015de9a848e8a9 AT gmail DOT com> <alpine DOT DEB DOT 2 DOT 00 DOT 1508311141070 DOT 6924 AT igor2priv>
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


> If I understood right, DJ's proposal sounds like a combination, where you 
> do not list the actual conncetions on the schematics but the possible 
> connections from which you select one during routing. (There's another 
> aspect with device/package mapping, but that's out of the scope here.)

Right, the netlister can allocate an initial gate/pin configuration
but the layout can change it.  The schematics *can* specify pin
numbers, but can also stick to symbolic pin names instead and let the
netlister handle it.