This repository has been archived by the owner on Jan 31, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
2 changed files
with
17 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,16 @@ | ||
--- | ||
layout: post | ||
--- | ||
|
||
This release says goodbye to the OOP programming interface. It's been an awkward fit for a combinator library. | ||
It has also proved to be too much work to maintain docs and tests for two interfaces with nothing but aesthetic | ||
benefit. | ||
|
||
I have also renamed the `or` and `and` functions to `alternatives` and `sequence` respectively. This should help to retain | ||
the natural language flow found in the OOP interface. It also brings our | ||
vocatulary more in line with other ecosystems. | ||
|
||
The `end` function has been reconfigured to not take a parser as input. Use it with `sequence` | ||
|
||
I have also added more example code in the `tests/Integration` folder. This includes an example of matching paremtheses (context free grammar) | ||
along with a more elaborate example in the form of a json parser. |