uu-parsinglib
What is uu-parsinglib?
New version of the Utrecht University parser combinator library, which provides online, error correction, annotation free, applicative style parser combinators. In addition to this we provide a monadic and an idomatic interface. Parsers do analyse themselves to avoid commonly made errors. This version is based on the module Data.Listlike, and as a result a great variety of input structures (Strings, ByteStrings, etc.) can be handled. The modules Text.ParserCombinators.UU.Demo.Examples, Text.ParserCombinators.UU.Idioms and Text.ParserCombinators.UU.Demo.MergeAndpermute contain a ready-made show_examples function, which can be called (e.g. from ghci) to see e.g. the error correction at work. It contains extensive haddock documentation, so why not just take a look to see the correction process at work, and to get a feeling for how the various combinators can be used? The file Text.ParserCombinators.UU.CHANGELOG contains a log of the most recent changes and additions. The file Text.ParserCombinators.UU.README contains some references to background information. We maintain a low frequency mailing for discussing the package. You can subscribe at: http://lists.science.uu.nl/mailman/listinfo/parsing.
uu-parsinglib is a tool in the Build Automation category of a tech stack.
uu-parsinglib Pros & Cons
Pros of uu-parsinglib
No pros listed yet.
Cons of uu-parsinglib
No cons listed yet.
uu-parsinglib Alternatives & Comparisons
What are some alternatives to uu-parsinglib?
NuGet
A free and open-source package manager designed for the Microsoft development platform. It is also distributed as a Visual Studio extension.
RubyGems
It is a package manager for the Ruby programming language that provides a standard format for distributing Ruby programs and libraries, a tool designed to easily manage the installation of gems, and a server for distributing them.
Bower
Bower is a package manager for the web. It offers a generic, unopinionated solution to the problem of front-end package management, while exposing the package dependency model via an API that can be consumed by a more opinionated build stack. There are no system wide dependencies, no dependencies are shared between different apps, and the dependency tree is flat.
