[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: LilyPond strings and \markup
From: |
Carl Sorensen |
Subject: |
Re: LilyPond strings and \markup |
Date: |
Sun, 16 Aug 2009 23:06:54 -0600 |
On 8/16/09 5:30 PM, "Joe Neeman" <address@hidden> wrote:
> On Sun, 2009-08-16 at 14:05 -0700, Mark Polesky wrote:
>> \version "2.13.4"
>>
>> %%%%%%%%%%%%
>> % QUESTION 1
>>
>> % "quoted string" is STRING
>> strA = "quoted string"
>>
>> % #"hash-quoted string" is SCM_TOKEN
>> strB = #"hash-quoted string"
>>
>> % these are both 'unexpected STRING_IDENTIFIER's:
>> % \strA \strB
>>
>> % Why isn't \strB an 'unexpected SCM_IDENTIFIER'?
Because \[alphanum]+ is a STRING_IDENTIFIER.
Remember, these are *parser* error messages. They come from interpreting
the symbols in the input stream, not from evaluating the variables resulting
from parsing the input stream.
The error message happens when the parser sees the text, not when the parser
evaluates the text.
unexpected * messages come when the parser splits things into tokens and
they don't match patterns defined for the rule the parser is trying to
match.
Carl
- LilyPond strings and \markup, Mark Polesky, 2009/08/16
- Re: LilyPond strings and \markup, Patrick McCarty, 2009/08/16
- Re: LilyPond strings and \markup, Joe Neeman, 2009/08/16
- Re: LilyPond strings and \markup,
Carl Sorensen <=
- Re: LilyPond strings and \markup, Mark Polesky, 2009/08/17
- Re: LilyPond strings and \markup, Trevor Daniels, 2009/08/17
- Re: LilyPond strings and \markup, Joe Neeman, 2009/08/17
- Re: LilyPond strings and \markup, Graham Percival, 2009/08/17
- Re: LilyPond strings and \markup, Neil Puttock, 2009/08/17
- Re: LilyPond strings and \markup, Graham Percival, 2009/08/17
- Re: LilyPond strings and \markup, John Mandereau, 2009/08/18
- Re: LilyPond strings and \markup, Nicolas Sceaux, 2009/08/18