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 <thomasmorle...@gmail.com> wrote: > 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 the guile-mailing list, in > memory-trace.scm we could do something at the lines of > > ;; TODO if lilypond moves to guile-2.2 merge the next two settings > (use-modules (lily) > (ice-9 format)) > (if guile-v2 (use-modules (ice-9 threads))) > > This would even be compatible with guile-1.8 (ofcourse one would do it > with a little different coding) > > Though, I think we currently have no need for it. So importing (ice-9 > threads) would be pointless. > If I'm right in this, would there be any other way to avoid this > warning-messages? > > > Cheers, > Harm > > _______________________________________________ > lilypond-devel mailing list > lilypond-devel@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-devel -- Han-Wen Nienhuys - hanw...@gmail.com - http://www.xs4all.nl/~hanwen _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
