summaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorJuan Manuel Tomás <jtomas1815@gmail.com>2024-10-19 20:03:50 -0300
committerJuan Manuel Tomás <jtomas1815@gmail.com>2024-10-19 20:03:50 -0300
commit16169311d2d39d82a799fd90c77c829767842c9d (patch)
treefab553bbf2003ac132b50e41f65326c9d6051489 /README.md
parenta60d9bd972f31a79aa0f0f8b10585187dc418fe8 (diff)
downloadmonparser-16169311d2d39d82a799fd90c77c829767842c9d.tar.gz
monparser-16169311d2d39d82a799fd90c77c829767842c9d.zip
Revert some changes
Diffstat (limited to 'README.md')
-rw-r--r--README.md25
1 files changed, 0 insertions, 25 deletions
diff --git a/README.md b/README.md
index 6705ffd..9e0546d 100644
--- a/README.md
+++ b/README.md
@@ -3,28 +3,3 @@ Parser Generator
This parser generator expands on [this paper](https://www.cs.nott.ac.uk/~pszgmh/monparsing.pdf).
The goal is to have a good enough parser generator for use in my other personal projects.
-
-# The type of parsers
-
-Parsers are lambdas that receive some *input* and return either a *parsing* or a *failure*.
-
-A *parsing* denotes a successful execution of the parser on the given input.
-
-Failures can be either *normal-failure* or *critical-failure*.
-
-The distinction of failure types allows to discern between an input that needs to be
-parsed with another parser, and a syntax error.
-
-## Interaction with parser control flow
-
-### Choice (either)
-
-- parsing -> exit
-- normal-failure -> continue
-- critical-failure -> exit
-
-### Sequence (comp)
-
-- parsing -> continue
-- normal-failure -> exit
-- critical-failure -> exit