bytestring-lexing: Parse and produce literals efficiently from strict or lazy bytestrings.

[ bsd3, data, library ] [ Propose Tags ]

Parse and produce literals efficiently from strict or lazy bytestrings.

Some benchmarks for this package can be found at:

[Skip to Readme]


Note: This package has metadata revisions in the cabal description newer than included in the tarball. To unpack the package including the revisions, use 'cabal get'.

Maintainer's Corner

Package maintainers

For package maintainers and hackage trustees


Versions [RSS] 0.1,,, 0.1.2, 0.2, 0.2.1, 0.3.0, 0.4.0, 0.4.2, 0.4.3,,,, 0.5.0,,,,,,,
Change log CHANGELOG
Dependencies base (>=4 && <5), bytestring (<0.11) [details]
License BSD-2-Clause
Copyright Copyright (c) 2012--2015 wren gayle romano, 2008--2011 Don Stewart
Author wren gayle romano, Don Stewart
Revised Revision 1 made by phadej at 2020-09-19T08:41:19Z
Category Data
Home page
Source repo head: darcs get
Uploaded by WrenThornton at 2015-06-07T00:48:12Z
Distributions Debian:, FreeBSD:, LTSHaskell:, NixOS:, Stackage:
Reverse Dependencies 40 direct, 7688 indirect [details]
Downloads 35346 total (157 in the last 30 days)
Rating (no votes yet) [estimated by Bayesian average]
Your Rating
  • λ
  • λ
  • λ
Status Docs available [build log]
Last success reported on 2015-06-09 [all 1 reports]

Readme for bytestring-lexing-

[back to package description]

This is a simple package and should be easy to install. You should
be able to use one of the following standard methods to install it.

    -- With cabal-install and without the source:
    $> cabal install bytestring-lexing
    -- With cabal-install and with the source already:
    $> cd bytestring-lexing
    $> cabal install
    -- Without cabal-install, but with the source already:
    $> cd bytestring-lexing
    $> runhaskell Setup.hs configure --user
    $> runhaskell Setup.hs build
    $> runhaskell Setup.hs test
    $> runhaskell Setup.hs haddock --hyperlink-source
    $> runhaskell Setup.hs copy
    $> runhaskell Setup.hs register

The test step is optional and currently does nothing. The Haddock
step is also optional.


An attempt has been made to keep this library portable. However,
the decimalPrecision function in Data.ByteString.Lex.Fractional
requires ScopedTypeVariables for efficiency. If your compiler does
not support ScopedTypeVariables, this should be easy enough to fix.
Contact the maintainer if this is an issue for you.

----------------------------------------------------------- fin.