[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Evolutionary User Strategery
From: |
Erik Sandberg |
Subject: |
Re: Evolutionary User Strategery |
Date: |
Sat, 8 Jul 2006 12:07:53 +0200 |
User-agent: |
KMail/1.9.1 |
On Friday 07 July 2006 16:46, Fairchild wrote:
> LilyPonders -
>
> The only reasonable solution is to maintain upward compatibility in the
> LilyPond processor. New features should be added without changing existing
> syntax. If it is deemed absolutely necessary to change semantics or define
> conflicting syntax, provide for optional interpretations based on the
> version specified. Older ly files should generate consistent results as
> LilyPond migrates. More exhaustive regression tests are necessary.
This one is not possible either: Let's say that you typeset a score in v2.4,
and that lily, due to a bug, makes some text collide with some notes. Let's
say that you work around this by tweaking the extra-offset of the text. If
now the bug is fixed in v3.0, your text will look ugly when compiled in 3.0,
and you will have to remove the tweak manually, regardless of how clever
convert-ly is.
Conclusion: Full backward compatibility is not desirable.
--
Erik
- Evolutionary User Strategery, Fairchild, 2006/07/07
- Re: Evolutionary User Strategery, Kieren MacMillan, 2006/07/07
- Re: Evolutionary User Strategery,
Erik Sandberg <=
- Re: Evolutionary User Strategery, Trevor Bača, 2006/07/08
- Re: Evolutionary User Strategery, Joshua Parmenter, 2006/07/08
- RE: Evolutionary User Strategery, Fairchild, 2006/07/08
- Re: Evolutionary User Strategery, Kieren MacMillan, 2006/07/08
- Re: Evolutionary User Strategery, Erik Sandberg, 2006/07/09
- RE: Evolutionary User Strategery, Fairchild, 2006/07/09
- Re: Evolutionary User Strategery, Kieren MacMillan, 2006/07/09
- RE: Evolutionary User Strategery, Fairchild, 2006/07/09
- Re: Evolutionary User Strategery, Kieren MacMillan, 2006/07/09
- Re: Evolutionary User Strategery, Erik Sandberg, 2006/07/10