@@ -46,7 +46,7 @@ https://gitlab.isc.org/isc-projects/kea/wikis/designs/simple-parser-design.
4646@section parserBisonIntro Flex/Bison Based Parser
4747
4848To solve the issue of phase 1 mentioned earlier, a new parser has been developed that is based on
49- the " flex and " bison" tools. The following text uses DHCPv6 as an example, but the same principle
49+ the flex and bison tools. The following text uses DHCPv6 as an example, but the same principle
5050applies to DHCPv4 and D2; CA will likely to follow. The new parser consists of two core elements
5151with a wrapper around them. The following descriptions are slightly oversimplified in order to
5252convey the intent; a more detailed description is available in subsequent sections.
@@ -115,12 +115,6 @@ meson setup build
115115meson compile -C build grammar
116116@endcode
117117
118- Strictly speaking, the comment "make parser" is not necessary. If you updated the .ll or .yy file,
119- the regular "make" command should pick those changes up. However, since one source file generates
120- multiple output files and you are likely to be using a multi-process build (by specifying the "-j"
121- switch on the "make" command), there may be odd side effects: explicitly rebuilding the files
122- manually by using "make parser" avoids any trouble.
123-
124118One problem brought on by use of flex/bison is tool version dependency. If one developer uses
125119version A of those tools and another developer uses B, the files generated by the different version
126120may be significantly different. This causes all sorts of problems, e.g. coverity/cpp-check issues
@@ -450,7 +444,7 @@ Here's the complete set of changes that were necessary.
450444 ;
451445 @endcode
452446
453- 5. Regenerate the flex/bison files by typing "make parser".
447+ 5. Regenerate the flex/bison files by typing "meson compile parser".
454448
4554496. Run the unit-tests that you wrote before you touched any of the bison stuff. You did write them
456450 in advance, right?
0 commit comments