X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Date: Thu, 6 Jul 2017 14:48:28 +0200 (CEST)
From: Roland Lutz <rlutz AT hedmen DOT org>
To: "Vladimir Zhbanov (vzhbanov AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Subject: Re: [geda-user] Refdes= mangling
In-Reply-To: <CAMvDHVCoOGz0JZ8KgAkzdzZJe6F1Q+eV--obH8QURAfNveGQCA@mail.gmail.com>
Message-ID: <alpine.DEB.2.20.1707061435520.1612@nimbus>
References: <CAMvDHVCoOGz0JZ8KgAkzdzZJe6F1Q+eV--obH8QURAfNveGQCA AT mail DOT gmail DOT com>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
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

Hi Vladimir,

I'm still not sure why you are trying to re-create the efforts I have 
already made refactoring gnetlist.

On Thu, 6 Jul 2017, Vladimir Zhbanov (vzhbanov AT gmail DOT com) [via 
geda-user AT delorie DOT com] wrote:
> Now, one of my ideas is to move mangling of hierarchy related attributes 
> to the post-processing stage in order to process schematic pages and 
> subpages separately, creating isolated subcircuits first.

As you may be aware, gnetlist already does this.  The parts of a schematic 
page which can be processed in a useful way without knowledge of the rest 
of the hierarchy tree are stored in a `schematic blueprint' structure. 
Then, for each instantiation of the subschematic in the hierarchy, a 
`schematic instance' structure is created and connected to the appropriate 
nets.

Roland