[prev in list] [next in list] [prev in thread] [next in thread] 

List:       lilypond-devel
Subject:    Re: Quotes around \consists argument?
From:       Luca Fascione <l.fascione () gmail ! com>
Date:       2022-04-25 14:43:40
Message-ID: CAN3Q5Nhv4VQ4s9JHZjDast+Kc_DbHGk4ENHcekHHHcLJGKuO7g () mail ! gmail ! com
[Download RAW message or body]

*understood, of course

On Mon, 25 Apr 2022, 14:14 Luca Fascione, <l.fascione@gmail.com> wrote:

> Yes I underground that, I was meaning for person's mental parsers, it
> helps that tokens (in an informal sense) always look the same
>
> L
>
> On Mon, 25 Apr 2022, 14:01 David Kastrup, <dak@gnu.org> wrote:
>
>> Luca Fascione <l.fascione@gmail.com> writes:
>>
>> > I think this is because it being an unquoted string (PERLfolk call these
>> > barewords) makes it feel more like an identifier, even if technically
>> it's
>> > a string (for the time being).
>> > It also has some advantages for example it's easier to work with names
>> > being always unquoted when you're grepping for them, kinda scenario
>> >
>> > I think things that work like language-level names, for this reason,
>> should
>> > flow unquoted, even if this requires effectively supporting barewords.
>>
>> LilyPond's input syntax treats strings and unquoted words identical in
>> most circumstances: essentially you can use quote marks to have things
>> interpreted as a single word that would otherwise be split into several
>> syntactic entities or be considered a notename (for example).
>>
>> --
>> David Kastrup
>>
>
[prev in list] [next in list] [prev in thread] [next in thread]