Re: [guile-2.2] threads

2017-04-05 19:58 GMT+02:00 Han-Wen Nienhuys : > LilyPond has no thread-safety anywhere. It would be actively harmful > if anybody ever tried to run something on a different thread. If > anything, you should find a way to forbid importing the threads > package. > > On Sun, Mar

Re: [guile-2.2] threads

On Wed, Apr 5, 2017 at 8:17 PM, David Kastrup wrote: > Han-Wen Nienhuys writes: > >> LilyPond has no thread-safety anywhere. It would be actively harmful >> if anybody ever tried to run something on a different thread. > > The Boehm GC garbage collector defaults

Re: [guile-2.2] threads

Han-Wen Nienhuys writes: > LilyPond has no thread-safety anywhere. It would be actively harmful > if anybody ever tried to run something on a different thread. The Boehm GC garbage collector defaults to running in its own thread. It is set to "Java" collection semantics which

Re: [guile-2.2] threads

LilyPond has no thread-safety anywhere. It would be actively harmful if anybody ever tried to run something on a different thread. If anything, you should find a way to forbid importing the threads package. On Sun, Mar 26, 2017 at 2:40 PM, Thomas Morley wrote: > Hi all,

[guile-2.2] threads

Hi all, guile-2.2 prints a warning, if module (ice-9 threads) is not imported. (This does not happen with guile-1.8 or guile-2.0) Import (ice-9 threads) to have access to `call-with-new-thread'. Import (ice-9 threads) to have access to `current-thread'. As suggested by Arne Babenhauserheide from