Re: Updating library code

2015-10-23 Thread Paul Morris
> On Oct 23, 2015, at 6:43 AM, Urs Liska wrote: > > How are you dealing with keeping code working and consistent? One simple thing I do, FWIW, is to add a short prefix to all my own functions. For example, instead of "do-something", I'd call it "cn-do-something". That way it’s clear which fu

Re: Updating library code

2015-10-23 Thread Michael Gerdau
[description of the problem of refactoring and code consistency in lilpond libs - snipped ] > So in essence what we need is a convert-ly-like tool for openLilyLib, > either as an independent tool or by somehow hooking into convert-ly > itself. Quite some time ago I opened an issue about this and w

Updating library code

2015-10-23 Thread Urs Liska
>From an openLilyLib perspective I have a question for all of you who maintain their personal LilyPond code libraries: How are you dealing with keeping code working and consistent? What I mean is: Syntax changes in LilyPond can be handled (mostly) with convert-ly. But what happens when a) a LilyPo