|
|
On March 29, 2005 06:44 am, "Alexander Carôt" wrote:
> > Another typical thread-programming question. I think I might make some
> > money by writing a book on thread programming - but I am sure that there
> > are enough (unread) books on it ...
> >
> > Well, as long as you do not use synchronization points in your code,
> > each thread runs independent of each other. There is no prediction which
> > thread is picked up at a given time. So, if your threads are _not_
> > independent of each other, you have to model this dependency in your
> > code by introducing synchronisation points.
>
> Well, the weired thing is that it works on every other machine except one
> new which is why I was concerned about some other problems with this.
>
> But still I'm gonna check on this and get back to you.
>
> Thanks anyway
People estimate that multithreaded programming is two to three times more
effort than single-threaded programming. It is because of things like this.
Also, because you essentially need to 'Prove' your code is correct, you
absolutely cannot rely on your debugger to catch mistakes.
--
chris@xxxxxxxxxxxxxxxxx, chris@xxxxxxxxxxxxx
--
List archive and information: http://lists.trolltech.com/qt-interest/
|
|