[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: threads
From:       Stephan Kulow <coolo () kde ! org>
Date:       1999-12-03 12:06:36
[Download RAW message or body]

"Dirk A. Mueller" wrote:
> 
> On Fre, 03 Dez 1999, Stephan Kulow wrote:
> 
> > I would say QString is as thread-safe as a const char*. And as someone
> > pointed out this all is no real problem with user-space threads.
> > It just makes parallel programming (reading a dir and displaying it)
> > more intuitive.
> 
> user space threads won't help you with blocking i/o. for non-blocking I/O,
> QTimers also work all right, and IMHO they're much easier to handle.
> 
> So unless we use preemtive threads everywhere (which is impossible), we
> can't gain anything, except a big layer of complexity that QTimer
> currently makes it easy to handle.
> 
> I can only repeat that debugging a multithreaded app is a pain, even if you
> have a gdb that knows about threads (in general it doesn't!). You spend half
> a day finding an unitialized pointer where a single-threaded app would crash
> right away and you'll fix it within 5 minutes.
> 
> Threads _will make_ development 10x more complicated, and I don't think any
> of the non-core KDE developers will like that move, especially as our
> productiveness will only be 10% of the previous value after the switch.
> 
Did anyone say that we will make it mandatory to use it?

Greetings, Stephan

-- 
As long as Linux remains a religion of freeware fanatics,
Microsoft have nothing to worry about.  
                       By Michael Surkan, PC Week Online

[prev in list] [next in list] [prev in thread] [next in thread]