Re: overriding voiceOne to add properties to that specific voice context

[Maurits Lamers]

Hey,
> 
> Computers have this wonderful facility called a "copy".
I know, and also version systems like git :)

> 
>> I would definitely love to bring the entire system to the most recent
>> version of Lilypond, or at least 2.18.2 (which is the version
>> installed by default under Ubuntu 18.04LTS and all derivatives), but
>> at the moment I think it could cause problems that would stand in the
>> way of the main objective, which is a working music braille output for
>> Lilypond.
> 
> You mean, a "working" music Braille output for an ancient historical
> version of LilyPond that does not compile on current systems, likely
> runs limited to 32bit, has much worse programming features and has no
> useful online support by current users and programmers because everyone
> has moved on.
> 
> To get anywhere useful except for a single-shot project, you'll not get
> around upgrading, and upgrading may make getting anywhere useful easier.
> 
> Just saying.

I appreciate your concern, but I think you might have misunderstood me a bit.
I do most of my work in 2.18 at the moment, and I try to provide workarounds 
for 2.14 where necessary.
The only areas where I have been needing adjustments for 2.14 have been the way 
listeners are added to contexts.
These adjustments also still work in 2.18 and as a result, the braille system 
works fine in 2.18.2. I haven't tested it yet on 2.20.

As my work is mostly done in Scheme, I am having more issues due to the rather 
old version of Guile that Lilypond runs on than limitations by Lilypond itself.
Lilypond 2.14.1 was released in on the 11th of July 2011, but if I am not 
mistaken even the most recent Lilypond uses a version of guile that was 
released on the 5th of July 2009 (1.8.7).
Don't get me wrong: that is what happens when things work fine, and upgrading 
is costly. I am fine with that and will try to work around whatever issues I 
encounter.

cheers

Maurits