[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Replacement for "parser"
From: |
David Kastrup |
Subject: |
Re: Replacement for "parser" |
Date: |
Sat, 30 Jul 2016 19:10:43 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux) |
Malte Meyn <address@hidden> writes:
> Am 30.07.2016 um 18:30 schrieb Hans Åberg:
>>
>>> 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)
>
> This won’t work in 2.19.45, it has to be #(define-music-function (ET
> midc m) …
Says who? It's nicer that way, but the old-style definition will most
certainly work as well.
> I just searched for the file and found it at
> http://x31eq.com/lilypond/ It looks like an older version of lilypond
> was used. But I don’t know which one because the author didn’t include
> a \version statement. This makes updating the code hard because you
> cannot simply use convert-ly.
convert-ly -f 2.18.0 -ed ...
Or any other version known to have worked.
> \version is nice to have. But maybe it should be made mandatory.
Maybe people should not ignore warnings. A hard error still does not
seem warranted.
--
David Kastrup
- Replacement for "parser", Hans Åberg, 2016/07/30
- Re: Replacement for "parser", Malte Meyn, 2016/07/30
- Re: Replacement for "parser", Hans Åberg, 2016/07/30
- Re: Replacement for "parser", David Kastrup, 2016/07/30
- Re: Replacement for "parser", Urs Liska, 2016/07/30
- Re: Replacement for "parser", Hans Åberg, 2016/07/30
- Re: Replacement for "parser", Hans Åberg, 2016/07/30
Re: Replacement for "parser", David Kastrup, 2016/07/30