Goldie: If You Use Trunk

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

- Requirements
- Download / Install
- Never Used a Parsing Tool?
- How To Use Goldie
- Grammar Definition Language
- Message Board
- Ticket System

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 Dynamic
- Calculator Static
- Parse Anything

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

- Library Source and StaticLang

Goldie Home (v0.4) -> If You Use Trunk

# If You Use Trunk

Users of the official Goldie releases can safely ignore these notes. If you don't know what "trunk" is, then don't worry about it, these notes don't apply to you.

Using a trunk version of Goldie is not recommended. However, if you wish to use the trunk anyway, there are a few things you should be aware of:

- The documentation (except for this "If You Use Trunk" notice) may be out-of-date for you.

- All the usual caveats and potential problems of using trunk software apply (if you're using trunk, you already know what those issues are).

- ** IMPORTANT **: Instead of the revision of SemiTwist D Tools mentioned in this documentation, you will need to use whatever SemiTwist D Tools revision was the most recent one before the date and time that your revision of Goldie was committed.

  Yes, that is complicated. In fact, that is the main reason using Goldie trunk is not recommended. However, this issue only exists because SemiTwist D Tools is still in an early state. This will change as SemiTwist D Tools matures.

If you're ok with all of this, then feel free to use Goldie trunk.

### A Note About the SVN Comments

Most of the messages on the SVN commits start with a prefix of either (B) or (NB):

(B): Breaking changes (ie, "This commit may include breaking changes.")

(NB): Non-Breaking changes (ie, "Unless I messed up, this commit contains non-breaking changes only.")

Be aware though, that even a (NB) revision might still require static-style languages to be re-generated with StaticLang.