Re: 48 and 72 ET

[Hans Åberg]

> On 10 Feb 2017, at 00:55, Simon Albrecht <address@hidden> wrote:
> 
> On 10.02.2017 00:19, Hans Åberg wrote:
>> If LilyPond knows how to run the code via convert-ly, why does it not do it?
> 
> LilyPond itself doesn’t change the code it is reading. convert-ly is a 
> separate Python script.
> It might be a valid feature request, though, to have a command-line option 
> which makes LilyPond call convert-ly, if the \version statement points to an 
> older version, and then read the resulting code.

If a .ly file is outdated, LilyPond might run convert-ly to create a new .lyo 
file, if it not already exists and is newer than the original (as in a 
Makefile). Then run the .lyo file instead if it is newer.

> That would leave some things to be designed though, e.g. what would happen if 
> convert-ly issues ‘Not smart enough to update…’ – which happens?

Then one would get an error message, as if there was only a direct compile.