Re: input code

[Hans Åberg]

> On 13 Dec 2019, at 03:00, Freeman Gilmore <address@hidden> wrote:
> 
>> On Thu, Dec 12, 2019 at 4:40 PM Hans Åberg <address@hidden> wrote:
>> 
>> > On 12 Dec 2019, at 22:32, Freeman Gilmore <address@hidden> wrote:
>> > 
>> >> On Thu, Dec 12, 2019 at 3:01 PM Hans Åberg <address@hidden> wrote:
>> >> 
>> >> > On 12 Dec 2019, at 14:01, Freeman Gilmore <address@hidden> wrote:
>> >> > 
>> >> > I would like to understand how it work, if i can.
>> >> 
>> >> There is a lexer generated from a file lexer.ll by Flex, which divides 
>> >> the input stream into tokens, which are handed over to a parser generated 
>> >> from a file parser.yy by Bison.
>> > 
>> > 0k that helps.   The lexer looks like what i an looking for I think at 
>> > this point; and from what you said.   I have the lexer.ll, parser.yy and 
>> > ly_grammar.txt files.     Now I need to finger out what part of the lexer 
>> > code reads the note event.
>> 
>> Check out the Bison manual, which also has a C++ calculator example with 
>> sources in the distribution. One can generate a file .output from the .yy 
>> file which contains all processing of the grammar would it be needed. Use 
>> flex 2.5.37, because the C++ lexer in 2.6* is broken.
> 
> I do not know if i can do this but I will look in to it.   Flex is new to me 
> today.   .

In the lexer.ll file, you might search for the rules with a “return” in them, 
as that is how the yylex function turns over the tokens to the parser. The Flex 
manual describes the rules syntax.