attoparsec-parsec 0.0.0 → 0.0.1

raw patch · 2 files changed

+11/−2 lines, 2 filesPVP ok

version bump matches the API change (PVP)

API changes (from Hackage documentation)

Files

• attoparsec-parsec.cabal +9/−2
• src/Data/Attoparsec/Text/Parsec.hs +2/−0

@@ -1,5 +1,5 @@ name:             attoparsec-parsec-version:          0.0.0+version:          0.0.1 license:          MIT license-file:     LICENSE copyright:        (c) 2011, 2012 Simon Hengel@@ -17,7 +17,7 @@                   Attoparsec is an awesome and very fast library, but it still                   has a weak point: It does not generate very useful error                   messages on parse errors.  Compiling an Attoparsec parser-                  against Parsec can be useful in at least two situations.+                  against Parsec can be useful for at least two scenarios.                   .                   - Parsec can be used while developing Attoparsec parsers, so                     that you get better error messages on failing test cases.@@ -26,6 +26,13 @@                     from it's speed.  And on parse errors you can re-parse the                     input with Parsec, so that you can display a useful error                     message to the user.+                  .+                  A simple usage example is here:+                  <https://github.com/sol/attoparsec-parsec#readme>++source-repository head+  type: git+  location: https://github.com/sol/attoparsec-parsec  library   ghc-options:

@@ -14,6 +14,8 @@ --   backtrack on failing alternatives that consumed input.  With careful use --   of `try` it is possible to write parsers that behave consistent across --   Attoparsec and Parsec.  Read the next section for more on that.+--+-- A simple usage example is here: <https://github.com/sol/attoparsec-parsec#readme> module Data.Attoparsec.Text.Parsec (  -- * Writing parsers that behave consistent across Attoparsec and Parsec