Re: Replacement for "parser"

[Urs Liska]

Am 30. Juli 2016 18:30:57 MESZ, schrieb "Hans Åberg" <address@hidden>:
>
>> On 30 Jul 2016, at 18:21, Malte Meyn <address@hidden> wrote:
>
>>> That one, I discovered, but “parser” must be there in another
>location.
>> Are you sure? input/regression/note-names.ly doesn’t have parser or
>(*parser*) anywhere.
>
>Looking at the file I am actually using (with SMuFL glyphs), (*parser*)
>is not needed, but Graham’s file regular.ly has a line
>  retune = #(define-music-function (parser location ET midc m)
>    (rational? integer? ly:music?) m)
>

That's the old syntax. In current LilyPond you can (must?) leave out the 
"parser location" variables because they are now transparently passed to the 
function.
If you need either of them you can access them through the (* *) calls.

>
>
>_______________________________________________
>lilypond-user mailing list
>address@hidden
>https://lists.gnu.org/mailman/listinfo/lilypond-user

-- 
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.