Re: lilypond ChangeLog VERSION lily/duration-scheme...

[Han-Wen Nienhuys]

Erik Sandberg wrote:
> Citerar Han-Wen Nienhuys <address@hidden>:
>
> > Log message:
> >         * python/convertrules.py (conv): warning on \tempo{}
> >         
> >         * ly/performer-init.ly: set tempoWholesPerMinute.
> >         
> >         * lily/parser.yy (output_def_body): disallow \tempo in \midi{}
>
> Hi,
>
> Why can't \tempo in \midi just produce a tempoWholesPerMinute expression plus a
> warning? If we do that, we get two advantages:

because pulling apart \tempo is a bit hairy, and   inserting \context { 
 \Score } is also hairy. Furthermore \midi{\tempo } is an ugly wart.

> 1. we will be backward compatible for a while; users will have time to change
> syntax for their midi blocks.

I doubt whether people will do it. Maybe we'd better tweak convert-ly 
further to detect \midi { } as well, and simply do a real conversion.

> 2. We may get a more powerful alternative to convert-ly, which can handle
> \tempo; 

vaporware.

--

Han-Wen Nienhuys - address@hidden - http://www.xs4all.nl/~hanwen

LilyPond Software Design
 -- Code for Music Notation
http://www.lilypond-design.com