diff options
author | Kyle Gunger <kgunger12@gmail.com> | 2021-12-05 18:01:49 -0500 |
---|---|---|
committer | Kyle Gunger <kgunger12@gmail.com> | 2021-12-05 18:01:49 -0500 |
commit | 9fc8b79c79975e99ea314b5e767b6c204a91f0ff (patch) | |
tree | d9ada2d05ff48ef4b1ca3e573826a3fa05ad58b4 | |
parent | 8e123f912ab0376d14f9d70b9d4dbb693163ce0b (diff) |
[README] Fix list
-rw-r--r-- | README.md | 14 |
1 files changed, 7 insertions, 7 deletions
@@ -28,15 +28,15 @@ Binaries will be dumped in the "build" folder. Once you have built the parser, it can be invoked in the build folder with `./parse`. The cli options are as follows: - - `-writelevel <0, 1, or 2>` tells the parser at what stage it should stop parsing and output a file. - - `0` will output the list of tokens generated by the tokenizer. - - `1` will output the Abstract Syntax Tree as generated by the parser. - - `2` will output a "virtual program". This is what the interpreter acts on. - - The default value is `1` +- `-writelevel <0, 1, or 2>` tells the parser at what stage it should stop parsing and output a file. + - `0` will output the list of tokens generated by the tokenizer. + - `1` will output the Abstract Syntax Tree as generated by the parser. + - `2` will output a "virtual program". This is what the interpreter acts on. + - The default value is `1` - - `-in <file>` tells the parser what file to parse. This is the only manditory option. +- `-in <file>` tells the parser what file to parse. This is the only manditory option. - - `-out <file>` tells the parser where to write the data. The default is `out.tnt`. +- `-out <file>` tells the parser where to write the data. The default is `out.tnt`. ### Other notes |