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=simple; d=mail.ud03.udmedia.de; h=
	subject:to:references:from:message-id:date:mime-version
	:in-reply-to:content-type:content-transfer-encoding; s=beta; bh=
	AW3y4R8QxofMJiOKRBTJxu3rJ/lYrIewToq0TiMHmN8=; b=sd9BbwxBie1aiCZK
	wRONSw2UZbugLeHGrr2MsQppv2uFmoJXXKglKo8kHmVSuXRsYLOxoFYlUaoXbDPz
	neKs26QCCWVjpLcks08nLtZcWJAg1+fyVGJGcde99qVLZGIpojwuwn+PN8EZHnh+
	VuaA5tmujRhbU4Foi9BtudnBspg=
Subject:	Re: [geda-user] back annotation proposal (RFC)
To:	geda-user AT delorie DOT com
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>
From:	"Markus Hitter (mah AT jump-ing DOT de) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Message-ID:	<55E44609.3060606@jump-ing.de>
Date:	Mon, 31 Aug 2015 14:18:17 +0200
User-Agent:	Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
	Thunderbird/38.2.0
MIME-Version:	1.0
In-Reply-To:	<alpine.DEB.2.00.1508311141070.6924@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

Am 31.08.2015 um 11:51 schrieb gedau AT igor2 DOT repo DOT hu:
> My proposal assumes there is a way a "netlist patch" can be loaded in
> gschem. Probably the same way as pcb can load a new netlist into an
> existing/open pcb.

How does a user find out which kind of "patches" are allowed? To know this, the initial netlist has to have all the neccessary informations already, like which pin can be replaced with which other pin and under which conditions. Having all the logic in place one can go just as well without back-annotation.

Back-annotation is still possible, of course, but it's then more a user convenience to allow the user to see in gschem which pins were actually used. For those users which actually care about pin usage.


Markus

-- 
- - - - - - - - - - - - - - - - - - -
Dipl. Ing. (FH) Markus Hitter
http://www.jump-ing.de/

- Raw text -