Re: [Lilypond-auto] Issue 2856 in lilypond: Patch: Get along with use of grob-property instead of grob-property-path in overrides

[Marc Hohl]

Am 24.09.2012 12:04, schrieb address@hidden:
> Status: New
> Owner: ----
> Labels: Type-Enhancement Patch-new
>
> New issue 2856 by address@hidden: Patch: Get along with use of 
> grob-property instead of grob-property-path in overrides
> http://code.google.com/p/lilypond/issues/detail?id=2856
>
> Get along with use of grob-property instead of grob-property-path in 
> overrides
>
> LilyPond uses a willy-nilly mixture of grob-property and
> grob-property-path when generating overrides programmatically (the
> parser only uses grob-property-path).  Several override-reinterpreting
> commands and functionalities were not prepared to deal with this.
>
> http://codereview.appspot.com/6544060
A quick glance at the code shows

+                      (cond
+                       ((ly:music-property m 'grob-property #f) => list)
+                       (else
+                        (ly:music-property m 'grob-property-path)))))

what does the second line mean? I have never seen '=>' in a scheme program.

Sorry for this beginner's question...

Marc