Eto.Parse 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).

<package xmlns="http://schemas.microsoft.com/packaging/2011/08/nuspec.xsd">
  <metadata>
    <id>Eto.Parse</id>
    <version>1.1.0.0</version>
    <title>Eto.Parse</title>
    <authors>Picoe Software Solutions,Inc.</authors>
    <owners>Picoe Software Solutions,Inc.</owners>
    <licenseUrl>https://github.com/picoe/Eto.Parse/raw/master/LICENSE</licenseUrl>
    <projectUrl>https://github.com/picoe/Eto.Parse</projectUrl>
    <requireLicenseAcceptance>false</requireLicenseAcceptance>
    <description>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).</description>
    <summary>A recursive descent LL(k) parser framework for .NET</summary>
    <releaseNotes>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</releaseNotes>
    <copyright>Copyright 2013 by Curtis Wensley</copyright>
    <tags>parser generator regex irony grammar fluent yacc lex ebnf bnf gold</tags>
  </metadata>
</package>