Hi Graham, not really a Scheme expert here, but having collected some experience over time: Feel free to send your code to me. It shouldn't be too hard to make the necessary adjustments.
Lukas Graham King <lilyp...@tremagi.org.uk> schrieb am Fr., 11. Juli 2025, 20:19: > I think it was in lilypond 2.25.23 that tempoWholesPerMinute was > changed from a moment to a fraction. I understand and accept this > change; however, I'm struggling with its consequences. > > I have a scheme function (about 300 lines of code, including comments > and some lookup tables, and some minimal self-test code) that relies on > tempoWholesPerMinute. The function has for many years been included in > almost all my transcriptions of renaissance music, where its purpose is > to display markup for each change of mensuration/proportion and to > adjust the time-signature and midi tempo. > > I could re-write the function to use tempoWholesPerMinuteAsMoment, but > sooner-or-later I think this would come back to bite me. By the time > the "...AsMoment" backward-compatibility stuff is deprecated, I'll > probably be too old and stupid to cope. So now is the time to bite the > bullet and update the function with the new syntax. Trouble is, after > spending more time than I can really afford, I'm coming to the > conclusion that old age and stupidity are already taking their toll. > > There's nothing confidential in the code, just likely some > embarrassment for me, but clearly 300 l.o.c. plus explanations is too > long for this list, and I don't think I can create a MWE, so please > would one of the scheme experts here be prepared to take a look at it > offline? I'm happy to offer a bounty! > > in hope, > -- Graham > > >
