Goldie: Future Work

Goldie
Parsing System (v0.8)
Goldie Home (v0.8)
Getting Started

- Requirements
- Download / Install
- Never Used a Parsing Tool?
- Goldie Overview
- Beginner's Tutorial
- Grammar Definition Language
- Contact / Support
  - Message Board
  - Issue Tracking

Goldie's Tools

- DumpCGT
- GenDocs
  - Template Format
- GRMC: Grammar Compiler
- JsonViewer
  - Parse Tree Mode
- Parse
- StaticLang
- Other Tools

GoldieLib Overview

- Static And Dynamic Styles
- Ambiguous Symbols

GoldieLib Reference

- Base
- Exception
- class Language
- class Lexer
- class Parser
- struct Symbol
- class Token
- Ver

GoldieLib Sample Apps

- Calculator Static
- Calculator Dynamic
- Sample Generic Parse

CGT File Format
FAQ
Change Log
If You Use Git Master
Future Work
Developers

- Scripts for Developers
- Library Source and StaticLang

Goldie Home (v0.8) -> Future Work

# Future Work

Some ideas for future work on Goldie:

(Bold is high priority)

- #3: Lex/parse from a stream
- #8: Ability to "step through" lexing and parsing
- #9: Support for "indentation increase/decrease" virtual terminals
- #10: Write an alternative to JsonViewer from scratch in D
- #14: Support new GOLD v5.0 features
- #15: Support for custom virtual terminals
- Better API for manipulating parse trees once they're built
- More error checking on .cgt loading, and an optional "lenient loading" mode
- Enhancements to the base GOLD capabilities
- Optional alternate to .cgt format
- Support for "Composed" grammars (ex: C with preprocessor, C# with XML-doc-comments, PHP/Classic ASP with HTML)
- More types of parsing than just LALR(1)
- Make download/installation simpler.
- Allow parsing at compile-time (may require improvements to D's CTFE)
- Add a way to automatically map a parse tree into an AST.
- Better API for semantic errors and custom user-made errors.
- Consider replacing GenDocs with DDoc.

### See Also:

- Goldie's Issue Tracking