diff options
| author | Krasimir Angelov <kr.angelov@gmail.com> | 2017-09-06 12:38:42 +0200 |
|---|---|---|
| committer | Krasimir Angelov <kr.angelov@gmail.com> | 2017-09-06 12:38:42 +0200 |
| commit | 15d014abb825837f0fd7c9e17d5907001135faaf (patch) | |
| tree | bc569f465432042702dfaa240746b8c6db609588 /doc | |
| parent | 18f2135785a71a1e93519a060d40b7ba523cf03b (diff) | |
the parser in the C runtime can now detect incomplete sentences just like the parser in the Haskell runtime. This is also reflected in all bindings.
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/runtime-api.html | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/runtime-api.html b/doc/runtime-api.html index 966f5f15c..792dbed39 100644 --- a/doc/runtime-api.html +++ b/doc/runtime-api.html @@ -154,12 +154,12 @@ or by calling __next__ if you are using Python 3: </pre> </span> <span class="haskell"> -This gives you a result of type <tt>Either String [(Expr, Float)]</tt>. -If the result is <tt>Left</tt> then the parser has failed and you will -get the token where the parser got stuck. If the parsing was successful -then you get a potentially infinite list of parse results: +This gives you a result of type <tt>ParseOutput</tt>. +If the result is <tt>ParseFailed</tt> then the parser has failed and you will +get the offset and the token where the parser got stuck. If the parsing was successful +then you get <tt>ParseOk</tt> with a potentially infinite list of parse results: <pre class="haskell"> -Prelude PGF2> let Right ((e,p):rest) = res +Prelude PGF2> let ParseOk ((e,p):rest) = res </pre> </span> <span class="java"> |