hextream alternatives and similar packages
Based on the "Parsing" category.
Alternatively, view hextream alternatives based on common mentions on social networks and blogs.
-
trifecta
Parser combinators with highlighting, slicing, layout, literate comments, Clang-style diagnostics and the kitchen sink -
Earley
Parsing all context-free grammars using Earley's algorithm in Haskell. -
replace-megaparsec
Stream editing with Haskell Megaparsec parsers -
parser-combinators
Lightweight package providing commonly useful parser combinators -
scanner
Fast non-backtracking incremental combinator parsing for bytestrings -
descriptive
Self-describing consumers/parsers; forms, cmd-line args, JSON, etc. -
parsec-free
Parsec API encoded as a deeply-embedded DSL, for debugging and analysis -
incremental-parser
Haskell parsing combinator liibrary that can be fed the input and emit the parsed output incrementally -
data-stm32
ARM SVD and CubeMX XML parser and pretty printer for STM32 family -
replace-attoparsec
Stream editing with Haskell Attoparsec parsers -
hsemail
Haskell Parsec parsers for the syntax defined in RFC2821 and 2822 -
parsec-parsers
Orphan instances so you can use `parsers` with `parsec`. -
matrix-market-attoparsec
Attoparsec parsers for the NIST Matrix Market format -
attoparsec-parsec
An Attoparsec compatibility layer for Parsec -
record-syntax
A library for parsing and processing the Haskell syntax sprinkled with anonymous records -
attoparsec-expr
Port of parsec's expression parser to attoparsec. -
streaming-binary
Incremental serialization and deserialization of Haskell values. -
fuzzy-dates
Automatically detect and parse dates in many different formats -
antlrc
Haskell binding to the ANTLR parser generator C runtime library http://www.antlr.org/wiki/display/ANTLR3/ANTLR3+Code+Generation+-+C
Access the most powerful time series database as a service
Do you think we are missing an alternative of hextream or a related project?
README
hextream
This library provides Haskell-native, streaming-friendly XML parsers.
Parsers are organized into 3 layers of increasing abstraction level: low, middle and high. Applications will most probably want to rely on the high-level layer.
The library does not define a data type nor parser for a whole XML document. Instead, parsers operate on XML tokens of various sizes, to allow for a usage in a streaming context (e.g. using streaming-attoparsec
).
The implementation is based on the following specifications:
Caveats
The following parts of the XML standard are not supported:
- external entities
- parameter entities
- the doctype internal subset, except for general entity declarations