[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Thinking about another disruptive change
From: |
Reinhold Kainhofer |
Subject: |
Re: Thinking about another disruptive change |
Date: |
Tue, 15 Nov 2011 12:56:24 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux i686; rv:7.0.1) Gecko/20111031 Thunderbird/7.0.1 |
Am 2011-11-15 10:49, schrieb David Kastrup:
> The "principle of lazy complication" would keep material as simple as
> feasible until a more complicated version is asked for.
>
> That is, when a music function asks for a "scheme?" argument and the
> input is just c', it gets a pitch. If it asks for a "ly:music?" event,
> it gets a NoteEvent (not an EventChord). If it asks for an EventChord,
> it gets one.
> [...]
>
> All in all, such a change should make programming and inspecting data
> structures much more straightforward, and particularly save the
> programmer from the "let's see what complex structures Lilypond creates
> from simple input and devise a scheme how to get at the simple things we
> actually wanted" phenomenon.
>
> But it is definitely not going to be an upwards-compatible change.
What will be different for a normal user? I.e. What basic lilypond
notation will change? And what advanced notation will break with that
change?
Cheers,
Reinhold
--
------------------------------------------------------------------
Reinhold Kainhofer, address@hidden, http://reinhold.kainhofer.com/
* Financial & Actuarial Math., Vienna Univ. of Technology, Austria
* http://www.fam.tuwien.ac.at/, DVR: 0005886
* LilyPond, Music typesetting, http://www.lilypond.org