• Requirements
• Change Log
• Installation
• Building
• FAQ
• If You Use Trunk
• API Overview
  • Static And Dynamic Styles
  • Ambiguous Symbols
• API Reference
  • Base
  • Exceptions
  • static class Goldie
  • class Language
  • class Lexer
  • class Parser
  • struct Symbol
  • class Token
• Included Sample Apps
  • Calculator Dynamic
  • Calculator Static
  • Parse Anything
• Included Tools
  • DumpCGT
  • GenDocs
    • Template Format
  • JsonViewer
    • Parse Tree Mode
  • Parse
  • StaticLang
• Future Work
• Developers
  • Library Source and StaticLang

Parse

Parses any source according to any GOLD CGT file, and saves the resulting tokens and parse tree to JSON files. These JSON files can be inspected with the enhanced version of JsonViewer bundled with Goldie.

Example:

If the file extension of your source is the same as the name of a CGT file in the lang/ directory: For instance, the *.calc files (which just happen to also be in lang/, although they could be anywhere) are intended to be parsed with lang/calc.cgt.

If the file extension of your source is the same as the name of a CGT file in some other directory (the directory can be absolute or relative):

To use a specific CGT file (in the lang/ directory), instead of inferring from the extension:

If the CGT file is not in the lang/ directory, you'll have to use both -lang and -langdir (This limitation will be fixed in a future version.):

All of the examples above will create the following files in the same directory as valid_sample2.calc:

The .tk.json file contains the tokenization (ie, the result of the Lexing phase) of valid_sample2.calc.

The .pt.json file contains the parse tree (ie, the result of the Parsing phase) of valid_sample2.calc.

Either of the .json files can be opened in JsonViewer and will be browsable using JsonViewer's Parse Tree Mode.

Command-line parameters: