Applications and libraries/Program development
This page contains a list of libraries and tools in a certain category. For a comprehensive list of such pages, see Applications and libraries.
- 1 Applications
- 2 Editor support
- 3 Libraries
- Cpphs is a re-implementation (in Haskell) of the C pre-processor.
- DrIFT is a tool which allows derivation of instances for classes that aren't supported by the standard compilers. In addition, instances can be produced in separate modules to that containing the type declaration. This allows instances to be derived for a type after the original module has been compiled. As a bonus, simple utility functions can also be produced from a type.
- Strafunski is a Haskell bundle that provides support for generic programming in Haskell, based on the concept of a functional strategy. It consists of a combinator library (StrategyLib) and a precompiler (DrIFT-Strafunski).
- A program using Template Haskell must link with the TH library even if it contains no references to TH after it has been compiled. Zeroth is a preprocessor which allows modules to use TH without linking with the TH library. To do this, Zeroth evaluates the top level splices from a module and saves the resulting code.
- Haskell All-In-One
- Haskell All-In-One is a Haskell utility which will take a program implemented in multiple modules and convert it to a single module, for optimisation purposes.
- The Haskell Cabal is a Common Architecture for Building Applications and Libraries. It is an API distributed with GHC, NHC98, and Hugs which allows a developer to easily group together a set of modules into a package. It is the standard build system for new Haskell libraries and applications
- hmake, a Haskell-aware replacement for make
- Automatically keeps track of module dependencies (i.e. no need to write any Makefiles!). Can be used with any of the usual Haskell compilers (ghc, hbc, nhc98).
- Hasktags is a simple program that generates TAGS files for Haskell code. Together with a supporting editor (e.g. NEdit, XEmacs, or Vim) TAGS files can be used to quickly find the places where functions, data constructors etc. are defined.
- HotHaskTags is a reimplementation of HaskTags that is more aware of the structure of Haskell source. If you have multiple functions of the same name in a project and jump from a file, it will analyze the imports of that file (including qualified imports correctly) and jump to the one that is being referred to. Extended ctags format only (read: Vim only).
- Another reimplementation of hasktags which has a better understanding (than hasktags) of Haskell syntax. ctags files are generated in the traditional format only; where the same identifier is reused, gasbag attempts to determine the best one for inclusion in the ctags file.
- A version of the tags program for Haskell. It uses the standardised hssource and posix library, works with GHC 5.02.1. tags file has been checked to work with vim and nedit.
- HaRe -- The Haskell Refactorer
- Mechanical refactoring of Haskell code (across module boundaries). HaRe now supports many refactorings such as renaming identifiers, moving/introducing/inlining definitions, and so on. Those refactorings are not limited to a single module. HaRe can be accessed from either Vim or Emacs
- Haskell All-In-One
- This Haskell utility takes a program implemented in multiple modules and converts it to a single module. This way you get whole program optimization for compilers that do not support that. Resulting programs will be probably faster using this method.
- Tool for deriving hylomorphisms from a restricted Haskell syntax. It is based on the algorithm first presented in the paper "Deriving Structural Hylomorphisms From Recursive Definitions" at ICFP'96 by Hu, Iwasaki, and Takeichi.
- Tool for automatically suggesting program improvements - library functions you may have missed, instances of map or foldr etc.
Documentation and browsing
- Hoogle is a Haskell API search engine. It allows you to search for a function in the standard libraries by either name, or by approximate type signature.
- Haddock A Haskell Documentation Tool
- A tool for automatically generating documentation from annotated Haskell source code. It is primarily intended for documenting libraries, but it should be useful for any kind of Haskell code. Haddock lets you write documentation annotations next to the definitions of functions and types in the source code, in a syntax that is easy on the eye when writing the source code (no heavyweight mark-up). The documentation generated by Haddock is fully hyperlinked - click on a type name in a type signature to go straight to the definition, and documentation, for that type.
- IDoc A No Frills Haskell Interface Documentation System
- IDoc extracts interface documentation and declarations from Haskell modules based on standard Haskell layout rules and a small number of clues that the programmer embeds in interface comments. These clues have been designed to be visually non-imposing when displaying the source in a text editor. Interface documentation is rendered in standard markup languages (currently, only HTML is supported). IDoc has been designed to be simple to use and install.
- HDoc generates documentation in HTML format for Haskell modules. The generated documents are cross linked and include summaries and detailed descriptions for the documented functions, data types, type classes and instance declarations.
- This program generates an HTML document showing the module interfaces of a Haskell project. Convenient links are placed for easy browsing of the different modules of the project, and for quick access to the source code.
- HaSpell is a spelling and style checker for Haskell programs. It can detect spelling errors in comments in the program text, and optionally in the code itself. There is an option to detect metasyntactic variables (such as 'foo') and 'bad function prefixes' such as 'compute' and 'doThe' - these make the program less readable and generally indicate bad programming style.
- Lambdabot is a large, ad-hoc collection of Haskell development tools available for offline use. In particular, automatic point-free refactoring is available via a vim interface, as well as access to Hoogle, djinn, ghci, and much much more.
Tracing & debugging
Tracing gives access to otherwise invisible information about a computation. Conventional debuggers allow the user to step through the program computation, stop at given points and examine variable contents. This tracing method is quite unsuitable for Haskell, because its evaluation order is complex, function arguments are usually unwieldy large unevaluated expressions and generally computation details do not match the user's high-level view of functions mapping values to values.
- Buddha is a declarative debugger for Haskell 98 programs. It presents the evaluation of a Haskell program as a series of function applications. A typical debugging session involves a series of questions and answers. The questions are posed by the debugger, and the answers are provided by the user. The implementation of Buddha is based on program transformation.
- A compiler for a subset of Haskell. Running a compiled program creates an evaluation dependency tree as trace, a structure based on the idea of declarative debugging from the logic programming community. A debugging session consists of the user answering a sequence of yes/no questions.
- A Haskell program is first transformed by hat-trans and then compiled with nhc98 or ghc. At runtime the program writes a trace file. There are tools for viewing the trace in various ways: Hat-stack shows a virtual stack of redexes. Hat-observe shows top-level functions in the style of Hood. Hat-trail enables exploring a computation backwards, starting from (part of) a faulty output or an error message. Hat-detect provides algorithmic debugging in the style of Freja. Hat-explore allows free navigation through a computation similar to traditional debuggers and algorithmic debugging and slicing.
- A library that permits to observe data structures at given program points. It can basically be used like print statements in imperative languages, but the lazy evaluation order is not affected and functions can be observed as well.
- "Graphical Hood" - a Java-based graphical observation event viewer, building on Hood.
- Darcs is a cutting edge revision control system written in Haskell
- a tool for generating graphs of commit activity for darcs repositories.
- a small utility that:
- extracts version information from Cabal files,
- maintains version tags in darcs,
- computes patch levels by querying darcs,
- extracts the current context from darcs, and
- adds all this information to a source file
- Git storage re-implementation in Haskell, allowing to read and write objects from a Haskell program easily.
- a system to judge your derivative work's purpose and license is valid with Creative Commons License Works.
- Bark is a bug tracking system written in Haskell
- Colourise Haskell source code in HTML or ANSI terminal screen codes.
- A preprocessor for typesetting Haskell programs that combines some of the good features of pphs and smugweb. It generates LaTeX code from literate Haskell sources.
- Another tool helping literate programming in Haskell. It helps to maintain views in a literate programming project. For example, it is among the tools used for developing a compiler in an iterative way with manuals didactically reflecting these evolving series of versions deriving from the literal code (see Essential Haskell Compiler project). Thus, Shuffle gives us the possibility for making didactically the evolution of versions visible in the documentation, when this is needed. More generally, Shuffle gives us tangling and weaving possibilities of literate programming. I think it gives a way to think of literal program development in a more abstract way by supporting the concept of views (maybe a too far analogy: version control management -- e.g. darcs -- helps thinking of program development in a more abstract way, too). Shuffle works well together with lhs2tex.
- Ian Lynagh's Haskell2LaTeX takes a literate Haskell program, or any LaTeX document with embedded Haskell, and pretty-prints the Haskell sections within it. The most significant difference between Haskell2LaTeX and other programs with similar goals is is that Haskell2LaTeX parses the input rather than merely lexing it.
- A Latex style file by Andrew Cooke that makes literal programming in Haskell simple.
- A TeX package for typesetting literate scripts in TeX. The output looks much like the code from Chris Okasaki's book "Purely Functional Data Structures", doing syntax highlighting and converting ASCII art such as
alphato proper mathematical symbols. It should work with both LaTeX and plain TeX, and it does its magic without any annotations, directly on the source code (lambdaTeX uses an almost-complete Haskell lexical analyzer written entirely in plain TeX). You only have to add
\input lambdaTeXat the top of your source file, and manually typeset your literate comments so they look as good as the source code.
- Haskell Style for LaTeX2e
- by Manuel Chakravarty provides environments and macros that simplify setting Haskell programs in LaTeX.
Integrated Development Environments
- Crimson Editor
- Free source code editor for MS Windows. Haskell support files are included in the standard installation, but must be added to the editor via the options dialog.
- Syntax highlighting files for KDE's Kate
- Syntax highlighting file by Jeroen van Wolffelaar and Arjan van IJzerdoorn, which inludes all prelude functions, datatype, constructors, etc, all in separate groups.
- Xcode plugin for enabling syntax highlighting, Xcode projects compiling and linking, and a couple missing features, for Haskell
Some other, mostly obsolete, modes are available in CVS.
- A unit testing framework for Haskell, similar to JUnit for Java. With HUnit, the programmer can easily create tests, name them, group them into suites, and execute them, with the framework checking the results automatically. Test specification is concise, flexible, and convenient.
- A tool for testing Haskell programs automatically. The programmer provides a specification of the program, in the form of properties which functions should satisfy, and QuickCheck then tests that the properties hold in a large number of randomly generated cases. Specifications are expressed in Haskell, using combinators defined in the QuickCheck library. QuickCheck provides combinators to define properties, observe the distribution of test data, and define test data generators.
- HTF - The Haskell Test Framework
- The HTF lets you write HUnit tests and QuickCheck properties in an easy and convenient way. Additionally, the HTF provides a facility for testing programs by running them and comparing the actual output with the expected output (so called "file-based tests"). The HTF uses Template Haskell to collect all tests and properties, so you do not need to write boilerplate code for that purpose. Preprocessor macros provide you with file name and line number information for tests and properties that failed.
- Hspec is a testing framework for Haskell. It is roughly based on the Ruby library RSpec. Some of Hspec's distinctive features are: a friendly DSL for defining tests, integration with QuickCheck, SmallCheck, and HUnit, parallel test execution, and automatic discovery of test files.
- Hpc: Haskell Program Coverage
- Hpc is a tool-kit to record and display Haskell program coverage. Hpc includes tools that instrument Haskell programs to record program coverage, run instrumented programs, and display the coverage information obtained.
- Haskell Equational Reasoning Assistant
- Functional programmers often appeal to equational reasoning to justify various decisions made in both design and implementation. This page introduces the Haskell Equational Reasoning Assistant (HERA), an architecture that provides both a GUI level and a batch level Haskell rewrite engine inside a single tool.
- pQC: parallel QuickCheck
- pqc provides Test.QuickCheck.Parallel, a QuickCheck driver that runs jobs in parallel, and will utilise as many cores as you wish, with the SMP parallel GHC 6.6 runtime. It is simple, scalable replacement for Test.QuickCheck.Batch.
- A library for determining the amount of memory allocated at any point by a GHC program.
- GHC Internals library
- A GHC library for polymorphically deconstructing heap objects from within Haskell code.
- GHC Heap and Stable Table Printing library
- Two libraries for GHC. The first is for printing heap objects from within Haskell or C code. The second is for dumping the contents of the Stable Table which is used for Stable Pointers and Stable Names.
- Located errors, tracing and exceptions in Haskell.
- Haskell98 termination analyzer
- Checks termination of given start terms w.r.t. a Haskell program: