X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.98.4 at av02.lsn.net
Subject: Re: [geda-user] Project leadership (design error in the core of
 gschem)
To: geda-user AT delorie DOT com
References: <CAJXU7q_3XwthnN_8mp7B+-ShHeK+=7J=54ZavKBUG3S3bSKp2A AT mail DOT gmail DOT com>
 <CANEvwqiM7CKG+WpDRpG4L=HsmSEZ32=CBDyUhuk3ks-SNedL2Q AT mail DOT gmail DOT com>
 <43CC8F96-6452-40FA-9DFB-E0983721C19C AT noqsi DOT com>
 <alpine DOT DEB DOT 2 DOT 00 DOT 1512290406210 DOT 9035 AT igor2priv>
 <20151229094603 DOT 782092b57563336883546bfd AT gmail DOT com>
 <CAM2RGhQ363RydhBJKMnNX5sLOkD1K4qVwb-PPwov3MT3D6MfdQ AT mail DOT gmail DOT com>
 <449C2A4A-814E-4858-ACB3-82807A80BE8A AT noqsi DOT com>
 <CAM2RGhQD1b0NKLWNYyB-m1whgYJZeEH9syzSs4OZt+22D5hooA AT mail DOT gmail DOT com>
 <alpine DOT DEB DOT 2 DOT 00 DOT 1512300441390 DOT 9035 AT igor2priv>
From: John Griessen <john AT ecosensory DOT com>
Message-ID: <5683FC71.5080904@ecosensory.com>
Date: Wed, 30 Dec 2015 09:46:57 -0600
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Icedove/38.4.0
MIME-Version: 1.0
In-Reply-To: <alpine.DEB.2.00.1512300441390.9035@igor2priv>
Content-Type: text/plain; charset=windows-1252; format=flowed
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

On 12/29/2015 10:17 PM, gedau AT igor2 DOT repo DOT hu wrote:
> why gschem doesn't ask the netlist infra? Or why the netlist engine doesn't generate an ".lst" (staying with the object example)
> gschem can read? And why gschem tries to understand slotting in the first place, and doesn't leave it for the netlister?

I think a superset netlist to be output along with the normal "bare" netlist would be the best kind of "patch" for annotating
forward and back.

It is the kind of thing that will let you extract parasitic capacitances and stats about your design.
It could be a way to more easily and cleanly separate out chunks of schematic and layout for reuse -- when they did not start out 
as a module, but now are wanted to be modular.