[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: c#(+6 2)

From: Gianmaria Lari
Subject: Re: c#(+6 2)
Date: Wed, 14 Mar 2018 17:01:51 +0100

On 14 March 2018 at 10:13, David Kastrup <address@hidden> wrote:
Gianmaria Lari <address@hidden> writes:

> On 12 March 2018 at 10:06, Gianmaria Lari <address@hidden> wrote:
>> On 12 March 2018 at 09:25, David Kastrup <address@hidden> wrote:
>>> From the "Extending LilyPond" guide:
>>> 1.2.1 LilyPond Scheme syntax
>>> ----------------------------
>>> The Guile interpreter is part of LilyPond, which means that Scheme can
>>> be included in LilyPond input files.  There are several methods for
>>> including Scheme in LilyPond.
>>>    The simplest way is to use a hash mark ‘#’ before a Scheme
>>> _expression_.
>>>    Now LilyPond’s input is structured into tokens and expressions, much
>>> like human language is structured into words and sentences.  LilyPond
>>> has a lexer that recognizes tokens (literal numbers, strings, Scheme
>> [....]
>> Ok David, I think it's clear. Thanks a lot for the very detailed
>> explanation, I appreciated your help.
> David, in a musical _expression_ the scheme _expression_ #(.....) must return a
> musical _expression_. That's ok.
> In case of I'm not inside a musical _expression_, does lilypond expect that the
> scheme _expression_ #(.....)  return something compatible with what "is on
> the left"?
> For example in this (working) code, on the left we have "piece" that needs
> a string on the right. So, on the right the scheme _expression_ have to
> return a string to have working code. Is my comprehension correct?
> \version "2.19.81"
> \score { \header { piece = #(number->string 123) } \fixed c' { a a a a} }

I don't think that the type of assignments in header blocks and similar
is being checked.  But the later use of "piece" will require something
compatible with a "markup" which a plain quoted string is.

The difference between # and $ is mostly that # does not convey any
syntactical information to the parser and thus can be left unevaluated
until actually used in some _expression_.  $ produces a type relevant to
parsing, so you might get surprising "premature" evaluations when the
respective token is needed as a lookahead token for determining the

In situations like assignments, the syntactic role of # is clear so
using $ is rarely called for.

David Kastrup

ok, thank you David!

reply via email to

[Prev in Thread] Current Thread [Next in Thread]