CongoCC Parser Generator

key_differences

revusky (revusky@undisclosed.example.com) — 2023-07-08T07:25:41+00:00

Key Differences between CongoCC and Legacy JavaCC From the end user's point of view, the most important difference is that CongoCC has undergone quite a bit of re-design to make it much more usable “out of the box” than the legacy JavaCC. One of the most basic (and obvious) things that CongoCC provides is the

start_hacking

revusky (revusky@undisclosed.example.com) — 2023-05-06T17:25:10+00:00

Start Hacking! CongoCC is based on the idea that things should just work. If all you want to do is use the tool, all you need to do is download the file: There are no dependencies (aside from a JDK) and it should be runnable via: java -jar congocc.jar

technical_support

revusky (revusky@undisclosed.example.com) — 2023-05-06T17:23:13+00:00

Technical Support Our policy is that we only provide technical support for the latest version of the tool. That is the version that you can download at . Alternatively, your own build is fine as long as it is built from the latest version of the code

settings

revusky (revusky@undisclosed.example.com) — 2023-04-17T18:53:04+00:00

Here, by category, is a list of all the settings in CongoCC that can be set at the top of a grammar file. Options relating to File/Class/Package Naming By default, the tool has some naming conventions that, actually, you might as well use. For example, if your grammar lies in a file named

new_syntax_summary

revusky (revusky@undisclosed.example.com) — 2023-04-10T10:04:31+00:00

Overview of the Newer Streamlined Syntax The following is a summary of CongoCC's streamlined syntax from the perspective of somebody migrating from legacy JavaCC. Note that, unlike CongoCC's predecessor, JavaCC 21, CongoCC does not support the legacy syntax. Any existing grammar file must be converter. There is a utility available that automatically converts the legacy syntax to the streamlined syntax. You can pick up the

include

revusky (revusky@undisclosed.example.com) — 2023-03-03T16:20:32+00:00

The INCLUDE Statement Congo's INCLUDE statement allows you to break up your grammar file into multiple physical files. It would look like this typically: INCLUDE "IncludedGrammar.javacc" This feature is not present in legacy JavaCC. The motivation be

up_to_here

revusky (revusky@undisclosed.example.com) — 2023-03-03T14:26:56+00:00

The "Up-to-here" Marker The up-to-here marker =>|| and the up-to-here-plus marker =>|+n (where n is an integer) were introduced to be able to express lookahead in a more succinct and less err-prone manner than using the LOOKAHEAD from legacy JavaCC or even the terser

contextual_predicates

revusky (revusky@undisclosed.example.com) — 2023-03-03T14:23:26+00:00

Contextual Predicates A contextual predicate allows you to add conditions at choice points based on scanning back in the call/lookahead stack. We are not aware of any other parser generator tool that has this feature. The easiest way to describe this is with some actual examples.

congo:intro - created

revusky (revusky@undisclosed.example.com) — 2023-02-19T11:10:48+00:00

What is CongoCC? CongoCC is a code generator that generates: * A Tokenizer, a.k.a. Lexer or Scanner * A Recursive Descent Parser * A Tree Builder

start

revusky (revusky@undisclosed.example.com) — 2023-02-19T00:56:49+00:00

What is CongoCC? CongoCC is a more advanced version of the legacy JavaCC tool. The current version is the result of a huge amount of restructuring and refactoring with the following main goals: * To make the tool much more useful and usable, out of the box

new_settings_in_javacc_21

chamberlain (chamberlain@undisclosed.example.com) — 2022-02-15T05:28:07+00:00

Here is a list of settings that exist in JavaCC 21 but are not (and never were) present in the legacy JavaCC tool: * BASE_NAME This option is used to set the name of the parser, lexer, constants, and NFA data files instead of using the default naming convention that prefixes these files with the name of the grammar file. If this option is set to an empty string (BASE_NAME=