This week I’ve been working on another WebCore dependency, though a little different to the previous ones. To work well, it seems that WebCore needs a threading system. AROS doesn’t have one. I think WebCore can work with just its stubs, but I don’t want to. I want this done properly.
I started looking at how I might implement threads, and it seemed that the interface was general enough that it could be useful to as a shared library for other things besides WebCore to use. And so
thread.library was born.
Its almost ready. Threads work, mutexes work, conditions work. The only thing I’m dealing with is what to do when the main task exits while threads are still running. There’s a bunch of bad things that can happen, which I don’t have time to go into right now, but the best thing I can do is to simply detach the threads and allow them to continue running. See here for more details, though the description is out of date - the code is now doing option 1, and the
ThreadBase issues have been dealt with. The last thing to take care of is a small memory allocation issue that is causing a crash, but once thats done I’ll check it in to AROS subversion for anyone to use.
Update 2007-12-03: Code is now in AROS SVN, and will be available for use in tonight’s nightly and SDK builds. Be sure to read the README before starting.