Re: Issue 1265 in lilypond: Avoid compilation and run-time deprecation warnings from Guile V2

[lilypond]

Updates:
        Summary: Avoid compilation and run-time deprecation warnings from Guile 
V2
        Labels: Patch

Comment #2 on issue 1265 by address@hidden: Avoid compilation and  
run-time deprecation warnings from Guile V2
http://code.google.com/p/lilypond/issues/detail?id=1265

I have a patch available, builds and runs OK and runs reg-tests with Guile  
V1.8.7.
With Guile 1.9.12 compiles without deprecation warnings and runs up as far  
as it gets without the patch, but this time without the run-time  
deprecation warnings from libguile.

The patch is available for review at  http://codereview.appspot.com/2247041

One issue - there's a flower/include/guile-compatibility.hh with stuff in  
it to translate the new guile names back to the deprecated guile names.   
This is intended for Guile 1.6, which we don't support any more. Should I  
hack out the conditional compilation block as part of this change?  This  
thing is included by lily/include/lily-guile.hh.

Cheers,
Ian