[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [T-Merge Patch] Lock build to reduce build time

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Thu, 28 Apr 2011 08:53:17 +0200

On Wed, Apr 27, 2011 at 23:22, Oto BREZINA <otik_at_printflow.eu> wrote:
> On 2011-04-27 22:22, Oto BREZINA wrote:
>> second try
>>
>> It saves about 6  BuildAllScreen2ViewVector executions on start and
>> about 5 calls per reload.
>>
>> This is first approach for review (you may suggest better names) to
>> don't spend too much time with something wrong from base.
> Same with:
> Using array+enum instead of set of variables
> Better handling of update of locator

Haven't checked your patch yet (still in the office).
But I had an idea on how to deal with this without using
locks/counters/whatever:

How about using a separate class for the screen/view vector. Access to
the vector is controlled by the class methods. That way, you can just
set a flag "rebuild necessary", and the vector is then rebuilt on the
first read access.
With such an implementation, the vector really is only rebuilt when necessary.

Thoughts?

Stefan

-- 
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2725403
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-04-28 08:56:17 CEST

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.