KDE/kdevelop/lib/plugins/vcs/interfaces

[Matthew Woehlke]

Do we need exec()? What is the difference between 'exec();' and
'start(); wait()'? Except that wait() seems to have gotten lost at some
point, that is :-).

So I guess the question are:
- What happened to wait()? Should we have wait()?
- If we have wait() do we want exec() == start()+wait()?

-- 
Matthew

-----Original Message-----
From: Andreas Pakulat [mailto:apaku at gmx.de] 
Sent: Sunday, May 27, 2007 20:54
To: kde-commits at kde.org
Subject: KDE/kdevelop/lib/plugins/vcs/interfaces

SVN commit 668891 by apaku:

add exec() which runs the job in a synchronous way


 M  +14 -0     vcshelpers.h  


--- trunk/KDE/kdevelop/lib/plugins/vcs/interfaces/vcshelpers.h
#668890:668891 @@ -237,11 +237,25 @@
      */
     QString errorMessage();
 
+    /**
+     * The job is started and the method returns control to the caller
only
+     * after the job has finished.
+     *
+     * There's no need to setup signal/slot connections to be able to
use
+     * this method, all results are available after exec returned.
+     *
+     * @return the FinishStatus
+     */
+    FinishStatus exec();
+
 public Q_SLOTS:
     /**
      * The job is not allowed to emit any signals until this method has
been
      * called. A plugin may either really start the job here, or it may
      * buffer any signals before start has been called.
+     *
+     * This method executes the job in an asynchronous way and the job
+     * will emit signals.
      */
     void start();