From: Daniel F. <zyr...@zy...> - 2009-02-20 14:28:10
|
I am happy to have something like: abstract class OSThreadInterface static final osti; abstract create_mutex() ... etc. With a concrete singleton HyThreadInterface and PThreadInterface that calls the appropriate syscalls. This just pushes the ifdefs into Java, which might have an advantage. We have more flexibility to pull other things into here also. At one level this is not much different from the syscall solution, but it might make life easier. If others feel strongly I will defer. It is possible to conflate this with RVMThread, but I am less convinced this is the right thing to do. Having it separate should make it remain a crisp interface. On the question of condition variables vs. monitors, we pragmatically pick what is best for what we care about most now. Because you can implement them using each other, this isnt really a big deal now. We can make the system work first and change this without a lot of effort later, so lets not get hung up on it like it is a critical issue. Perhaps we change this when Harmony is our default implementation. It is really essential here that we try and cut to the core of what is important, it is too easy to get sucked into detail that really confuses the issue. The details fall into place once it is clear where we want to head. Cheers, Daniel. |