VCS Interface classes (async execution)

Andreas Pakulat apaku at gmx.de
Thu May 3 08:16:21 UTC 2007


On 03.05.07 09:33:26, Jakob Petsovits wrote:
> On Wednesday, 2. May 2007, Andreas Pakulat wrote:
> > Well, maybe I'm blind but I don't really see how this would work. I mean
> > we'd have to have such a wrapper class for each iface and the wrapper
> > class has to copy the API of the interface plus provide a way to report
> > back the result of executing a method. IMHO thats too much work, at
> > least waiting for a KJob to be finished is pretty easy and if needed we
> > can provide specialized KJobs which carry the return value in them (once
> > they are finished).
> 
> Ok, cool with me. I was just thinking it over without exactly evaluating the 
> feasability.

I'm also all for sharing threading-implementations, but maybe we already
have that with ThreadWeaver in kdelibs.

Andreas

-- 
Someone is speaking well of you.




More information about the KDevelop-devel mailing list