On 9 Sep 2006, at 15:11, Wim Oudshoorn wrote:
It is probably not worth it.
I agree.
But I am getting quite frustrated
with the multithreading problems, which unfortunately until
now all turned out to be problems in gnustep-base (which
is much harder for me to debug.)
Yes ... its big and complicated and threading is tricky :-(
That means that the base library code is the most likely place to
find any threading issues, as most user level applications avoid
threading difficulties by using facilities provided in the base
library (NSConnection for inter thread communication, perfoming a
selecotr in the main thread etc).
If you have any threading testcases you could contribute to the
testsuite, I would be really glad to have them ...
Also the fact that most
of the time when an actual dead lock occurs the stack trace is
garbled does not help.
That's why I hate threaded code ... I don't use threads in my
programs unless I really have to.
_______________________________________________
Bug-gnustep mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-gnustep
