Eto.Parse
1.1.0
See the version list below for details.
dotnet add package Eto.Parse --version 1.1.0
NuGet\Install-Package Eto.Parse -Version 1.1.0
<PackageReference Include="Eto.Parse" Version="1.1.0" />
paket add Eto.Parse --version 1.1.0
#r "nuget: Eto.Parse, 1.1.0"
// Install Eto.Parse as a Cake Addin #addin nuget:?package=Eto.Parse&version=1.1.0 // Install Eto.Parse as a Cake Tool #tool nuget:?package=Eto.Parse&version=1.1.0
Eto.Parse is a highly optimized recursive decent LL(k) parser framework that can be used to create parsers for complex grammars that go beyond the capability of regular expressions.
You can use BNF, EBNF, or Gold parser grammars to define your parser, code them directly using a fluent API, or use shorthand operators (or a mix of each).
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET Framework | net40 is compatible. net403 was computed. net45 was computed. net451 was computed. net452 was computed. net46 was computed. net461 was computed. net462 was computed. net463 was computed. net47 was computed. net471 was computed. net472 was computed. net48 was computed. net481 was computed. |
This package has no dependencies.
NuGet packages (1)
Showing the top 1 NuGet packages that depend on Eto.Parse:
Package | Downloads |
---|---|
FlipSky.MineCraft.Scripting
Package Description |
GitHub repositories
This package is not used by any popular GitHub repositories.
Breaking Changes for v1.1:
* Removed NamedParser and moved Name property to base Parser class
* ICharTester removed and all char testers are now derived from Parser directly (via CharTerminal), and names end in 'Terminal'
* Renamed LiteralParser to LiteralTerminal
* RepeatParser's '-' operator changed to '^' to specify the Until parser
* '-' operator is now used for an exception using the ExceptParser (to match ebnf syntax)
* NamedMatch/NamedMatchCollection are now named Match/MatchCollection
* NamedMatch.Value is now equivalent to Match.Text.
Other changes:
* More fairly significant performance improvements from restructuring
* Match.Value added which gets the appropriate object value from each parser (e.g. a number, boolean, escaped string, etc)
* Added BooleanParser
* Added option for speed test to compare the output of a property in the parsed json string