Hoed: Lightweight algorithmic debugging.
Hoed is a tracer and debugger for the programming language Haskell.
To locate a defect with Hoed you annotate suspected functions and compile as usual. Then you run your program, information about the annotated functions is collected. Finally you connect to a debugging session.
[Skip to Readme]
Modules
[Index]
Downloads
- Hoed-0.5.1.tar.gz [browse] (Cabal source package)
- Package description (as included in the package)
Maintainer's Corner
For package maintainers and hackage trustees
Candidates
| Versions [RSS] | 0.1.0.0, 0.1.0.1, 0.2.0, 0.2.1, 0.2.2, 0.3.0, 0.3.1, 0.3.2, 0.3.3, 0.3.4, 0.3.5, 0.3.6, 0.4.0, 0.4.1, 0.5.0, 0.5.1 |
|---|---|
| Change log | changelog |
| Dependencies | array, base (>=4 && <5), bytestring, cereal, cereal-text, cereal-vector, clock, containers, deepseq, directory, hashable (>=1.2.5), libgraph (==1.14), open-browser, primitive, process, QuickCheck, regex-tdfa, regex-tdfa-text, semigroups, strict, template-haskell, terminal-size, text, transformers, uniplate, unordered-containers, vector, vector-th-unbox [details] |
| License | BSD-3-Clause |
| Copyright | (c) 2000 Andy Gill, (c) 2010 University of Kansas, (c) 2013-2018 Maarten Faddegon |
| Author | Maarten Faddegon |
| Maintainer | hoed@maartenfaddegon.nl |
| Category | Debug, Trace |
| Home page | https://github.com/MaartenFaddegon/Hoed |
| Source repo | head: git clone https://github.com/MaartenFaddegon/Hoed.git |
| Uploaded | by faddegon at 2018-03-17T06:55:06Z |
| Distributions | |
| Reverse Dependencies | 4 direct, 0 indirect [details] |
| Downloads | 12518 total (7 in the last 30 days) |
| Rating | (no votes yet) [estimated by Bayesian average] |
| Your Rating | |
| Status | Docs available [build log] Last success reported on 2018-03-17 [all 1 reports] |
Readme for Hoed-0.5.1
[back to package description]Hoed - A Lightweight Haskell Tracer and Debugger
Hoed is a tracer and debugger for the programming language Haskell. To locate a defect with Hoed you annotate suspected functions and compile as usual. Then you run your program, information about the annotated functions is collected. Finally you connect to a debugging session.
Submit feature requests or contribute code on the
