Thanks for the clarification, now it is much clearer!
thSoft
On 2010.03.08., at 11:03, Bertalan Fodor (LilyPondTool) wrote:
> The lexer reads regular expressions, and tries to match them to a rule. A
> rule will return a token and a value (yylval). These two will be used by the
> parser to int
The lexer reads regular expressions, and tries to match them to a rule.
A rule will return a token and a value (yylval). These two will be used
by the parser to interpret the input.
This is so simple.
So for example how a note name is recognized:
a note name like fs will be read as [a-zA-Z\200-\
On 2010.03.04., at 19:36, Patrick McCarty wrote:
> 2010/3/4 Harmath Dénes :
>> Greetings all,
>>
>> it's great to have a grammar of LilyPond in the NR! But there are terminal
>> rules which are not strings (BOOK_IDENTIFIER, CHORD_MODIFIER etc.). Where
>> can their definitions be learned?
>
> I
2010/3/4 Harmath Dénes :
> Greetings all,
>
> it's great to have a grammar of LilyPond in the NR! But there are terminal
> rules which are not strings (BOOK_IDENTIFIER, CHORD_MODIFIER etc.). Where can
> their definitions be learned?
If you do a `git grep' for them in the source tree, you will se
Greetings all,
it's great to have a grammar of LilyPond in the NR! But there are terminal
rules which are not strings (BOOK_IDENTIFIER, CHORD_MODIFIER etc.). Where can
their definitions be learned?
Thanks in advance,
thSoft
___
lilypond-devel mailing
