On Saturday 09 April 2005 08:05, Benjamin Meyer wrote:
> In the docs for KIO::FileCopyJob::FileCopyJob it says: "Do not create a 
> FileCopyJob directly."
> 
> http://developer.kde.org/documentation/library/cvs-api/kio/html/classKIO_1_1FileCopyJob.html#a0
> 
> Why shouldn't I use FileCopyJob directly?

Because the KIO API is KIO::file_copy() or KIO::file_move().
For FileCopyJob it doesn't make much difference right now, but if you take
e.g. file_delete, that one can't be expressed in terms of "new <someJobclass>".

So for consistency, all jobs are created via a public function.

-- 
David Faure, faure@kde.org, sponsored by Trolltech to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<