AFAIK a normal user should see a warning for a deprecated property and an error for an API break. This is not the case: the user here sees a warning for an API break. Fortunately, out of deliberate fussiness, I made sure that my test cases already stop corresponding to warnings rather than just errors. But this was a personal choice which certainly does not guarantee the consistency of the API itself.
Il dom 9 feb 2025, 12:12 Werner LEMBERG <w...@gnu.org> ha scritto: > > >> proportionalNotationDuration is not deprecated. Its type has been > >> changed, therefore the warning about not accepting a moment is correct. > > > > that's what I was saying. Wouldn't it have been better to treat it > > as a deprecated property with an appropriate warning, rather than as > > an API break with a warning instead of an error? > > Dan implemented a solution for normal users, not for library > developers: if they run `convert-ly` on their input files, everything > will work just fine – they get warnings, but it will compile.
