X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-Injected-Via-Gmane: http://gmane.org/
To: geda-user AT delorie DOT com
From: Kai-Martin Knaak <kmk AT familieknaak DOT de>
Subject: Re: [geda-user] A different kind of gschem nap
Date: Mon, 08 Sep 2014 01:57:44 +0200
Lines: 21
Message-ID: <luirdo$uc0$1@ger.gmane.org>
References: <luh5iq$42s$1 AT ger DOT gmane DOT org> <98C89E6D-3A1B-4E11-8F2A-F0C9D5D2AE7D AT sbcglobal DOT net>
Mime-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7Bit
X-Complaints-To: usenet AT ger DOT gmane DOT org
X-Gmane-NNTP-Posting-Host: a89-182-24-175.net-htp.de
User-Agent: KNode/4.12.4
Reply-To: geda-user AT delorie DOT com

Edward Hennessy wrote:

> The function s_weakref_remove() is taking up a large percentage of
> the execution time. (More than 85%) And, this function is called
> from smob_free().
> 
> Using a faster container to store weak references could put us into
> the 2-3 min range.

This still seems ridiculously inefficient to me. The algorithm jut 
needs to assign about 100 refdes numbers that are not yet used. This 
should not take minutes on a contemporary desktop. 

I tried to use the autonumber dialog that can be from inside the 
gschem UI (Attributes->Autonumber_Text). It returns immediately within 
less than 0.1 s. Maybe, it is possible to hook into whatever method 
this renumber path uses. It could use the same options as the 
interactive dialog. I for one would welcome the additional user 
control on the process.

---<)kaimartin(>---