Do you want to convert various kinds of BNF to other kinds of BNF? No?
Well imagine if you did! This would be the tool for you.
Input: Various BNF-like syntaxes
Output: Various BNF-like syntaxes, AST dumps, and Railroad Syntax Diagrams
Compilation phases:
- Bold indicates the input BNF dialects with the most features
- โจ indicates presentational formats (these are the good ones!)
- ๐งช indicates debugging formats.
You don't want these unless you're looking at kgt's internals. - Other formats provide various subsets of features
Gallery:
- C89 grammar WSN source
โ Presentational BNF: EBNF
โ Railroad diagrams: SVG, ASCII, UTF8 โจ Look at these ones! โจ - C99 grammar EBNF source
โ Presentational BNF: EBNF
โ Railroad diagrams: SVG, ASCII, UTF8
Getting started:
See the /examples directory for grammars in various BNF dialects. These have been collated from various sources and are of various quality. BNF dialects tend to be poorly specified, and these examples are an attempt to keep a corpus of known-good examples for each dialect. kgt can't parse them all yet.
kgt reads from stdin in dialect -l ...
and writes to stdout
in format -e ...
:
; kgt -l bnf -e rrutf8 < examples/expr.bnf
expr:
โโโโโฎโโ term โโ "+" โโ expr โโโญโโโคโ
โ โ
โฐโโโโโโโโโ term โโโโโโโโโโโฏ
term:
โโโโโฎโโ factor โโ "*" โโ term โโโญโโโคโ
โ โ
โฐโโโโโโโโโ factor โโโโโโโโโโโฏ
factor:
โโโโโฎโโ "(" โโ expr โโ ")" โโโญโโโคโ
โ โ
โฐโโโโโโโโ const โโโโโโโโโโฏ
const:
โโโโ integer โโโคโ
and the same grammar output as SVG instead:
; kgt -l bnf -e svg < examples/expr.bnf > /tmp/expr.svg
Clone with submodules (contains required .mk files):
; git clone --recursive https://github.com/katef/kgt.git
To build and install:
; bmake -r install
You can override a few things:
; CC=clang bmake -r
; PREFIX=$HOME bmake -r install
You need bmake for building. In order of preference:
- If you use some kind of BSD (NetBSD, OpenBSD, FreeBSD, ...) this is make(1). They all differ slightly. Any of them should work.
- If you use Linux or MacOS and you have a package named bmake, use that.
- If you use Linux and you have a package named pmake, use that. It's the same thing. Some package managers have bmake packaged under the name pmake. I don't know why they name it pmake.
- Otherwise if you use MacOS and you only have a package named bsdmake, use that. It's Apple's own fork of bmake. It should also work but it's harder for me to test.
- If none of these are options for you, you can build bmake from source. You don't need mk.tar.gz, just bmake.tar.gz. This will always work. https://www.crufty.net/help/sjg/bmake.html
When you see "bmake" in the build instructions above, it means any of these.
Building depends on:
- Any BSD make.
- A C compiler. Any should do, but GCC and clang are best supported.
- ar, ld, and a bunch of other stuff you probably already have.
Ideas, comments or bugs: kate@elide.org