Hello Jean, hello everyone,
this does sound like a good idea. But what I've been thinking about for a while
is: For many incompabilities Lilypond could very well know how to handle
things. With things like music functions or grobs changing names we could
simply have a set of includes to make the previous version compatible with the
current one. This could then have compatibility functions, we could try
something to alias Grob names and properties and stuff. Then Lilypond 2.23.6
could automatically include the file for 23.5, for 23.4 and so on until we are
at the specified version upon encountering a version string. While this cannot
handle every possible change in format (it is not like convert-ly could) it
would be able to handle the most common problems with older language versions
automatically and non-destructively.
And with things that cannot be easily wrapped to the new functionality we could
throw an error, telling the user that something requires manual intervention.
Just some thoughts I had for some time.
Best,
Valentin
08.02.2022 23:53:32 Jean Abou Samra <j...@abou-samra.fr>:
> Le 08/02/2022 à 20:25, Jean Abou Samra a écrit :
>> - When the score produces an error and the \version
>> statement is for a different minor version number,
>> print a warning ("compilation failed and \version
>> statement is outdated, did you update syntax with
>> convert-ly?" or something like that).
>
>
> OK, I've opened
>
> https://gitlab.com/lilypond/lilypond/-/merge_requests/1187
>
> Let's continue the discussion there.
>
> Jean
