Re: Issue 1780 in lilypond: Scheme format functions with no destination parameter cause deprecation warnings in Guile V2

[lilypond]

Comment #5 on issue 1780 by address@hidden: Scheme format functions  
with no destination parameter cause deprecation warnings in Guile V2
http://code.google.com/p/lilypond/issues/detail?id=1780

Attached are two logs with the patch applied.  The Guile signal for for the  
(format #f ...) statement still happens, but there's no deprecation warning  
(see first log). I then tried working around by changing the call in  
titling-init.ly to
====
tagline = \markup {
  \with-url

  #"http://lilypond.org/";
  \line {

    %% 2014 = em dash.

    #(ly:export
<<<< Before fix
      (format "Music engraving by LilyPond ~a~awww.lilypond.org"
       (lilypond-version)
       (ly:wide-char->utf-8 #x2014)
       ))
====
      (string-concatenate
       (list  "Music engraving by LilyPond ~a~awww.lilypond.org"
         (lilypond-version)
         (ly:wide-char->utf-8 #x2014)
       )))
> > > > > with patch and work-round
  }
}
====
This changed the signal from Guile to another spot in titling-init.ly (see  
second log).

Cheers Ian




Attachments:
        testv2withpatch1.log  10.2 KB
        testv2withpatch2.log  9.1 KB