12 |
|
|
13 |
When you configure "--with-threads=null", you will get the usual |
When you configure "--with-threads=null", you will get the usual |
14 |
threading API (call-with-new-thread, make-mutex, etc), but you can't |
threading API (call-with-new-thread, make-mutex, etc), but you can't |
15 |
actually create new threads. |
actually create new threads. Also, "--with-threads=no" is now |
16 |
|
equivalent to "--with-threads=null". This means that the thread API |
17 |
|
is always present, although you might not be able to create new |
18 |
|
threads. |
19 |
|
|
20 |
The short term plan is to remove the support for --with-threads=no |
When cooperative threading is not supported on your platform, you will |
21 |
completely so that one doesn't need to special case as much when |
get the "null" threads. |
|
writing code that needs to be thread-aware but should also work |
|
|
without threads. |
|
22 |
|
|
23 |
The long term plan is to make the selection of a thread implementation |
The long term plan is to make the selection of a thread implementation |
24 |
a run-time option, not a configure time option. |
a run-time option, not a configure time option. |