Paul <p...@paulwmorris.com> writes: > So I assume (as a non-authority in this area) that the best way to > address the slowdown is to start using guile 2.0's compiler to compile > LilyPond's scheme code.
For scm/*.scm, yes. But LilyPond code does a lot by interpreting Scheme code via #... and $... . It may mean moving a lot of much-executed code out of *.ly to separate *.scm files, and we don't currently have a strategy for doing that at the LSR/user level anyway. > And I suppose taking that step would make sense after the known bugs > are fixed and things work using the interpreter, but are just slower. Well, "just" is at showstopper level. But I still think that it makes sense focusing on it once it has become trivial for Guile developers to reproduce and analyze the problems. It will be so much more easy to get them interested in contributing to significant improvements. -- David Kastrup _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
