Re: Evolutionary User Strategery

[Joshua Parmenter]

On Jul 8, 2006, at 3:07 AM, Erik Sandberg wrote:

Let's say that you typeset a score in v2.4, 

and that lily, due to a bug, 

But, since 2.4 is a stable release, wouldn't there be the expectation that  bugs were worked out before the next stable release is made, or that these "stable bugs" would be expected in convert-ly?

I realize (of course) that this is impossible... so maybe there need to be less stable releases, and hopefully more bug fixes and more actual stability to prevent much of the problem being discussed?

Josh

******************************************

Joshua Parmenter

address@hidden

Post-Doctoral Research Associate - Center for Digital Arts and Experimental Media

Raitt Hall - University of Washington

Seattle, Washington 98195

http://www.dxarts.washington.edu

http://www.realizedsound.net/josh/

On Jul 8, 2006, at 3:07 AM, Erik Sandberg wrote:

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

_______________________________________________

lilypond-user mailing list

address@hidden

http://lists.gnu.org/mailman/listinfo/lilypond-user