Chris Yate <chrisy...@gmail.com> writes: > On Sat, 1 Oct 2016 at 13:41 David Kastrup <d...@gnu.org> wrote: > >> > >> > The culprit is 2.19.21. >> >> Ah, that's likely to be not the real culprit but just the version where >> assertions started to be enabled by default on Windows (and other) >> builds. >> >> Of course, either warrant fixing if they occur. > > Hi David, > That's pretty interesting. The issue might have been around for years... > Were assertions ever enabled in builds previous to 2.19.21?
Not that I know of. They were enabled in Patchy runs (namely for the normal review testing) but of course that only covers a limited number of test documents. So we have been seeing a bit of fallout from finally enabling the assertions by default that previously just went under the radar. -- David Kastrup _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
