Wanted libraries

From HaskellWiki
Revision as of 20:51, 14 February 2008 by Monadinous (talk | contribs)
Jump to navigation Jump to search

This page provides a list of missing and found libraries for solving common real world programmer tasks.

If you think there should be a library for some common task, add it to this page, and someone may well step up and write it. If you know of a library to solve an open problem domain, link to it.

The first place to look is the full libraries list.


Missing libraries (by problem domain)

IMAP

A functional IMAP library would be nice, particularly one that can be used in conjunction with encryption and authentication. References have been found to a SoC project although it appears to be derelict.

Numerical algorithms

Stuff to compute bessel functions, struve H1 etc.

.NET/Java Interoperability

We could use a .NET FFI library that lets you easily call into the .NET framework. Perhaps the (abandoned?) Hugs .NET FFI library could be resurrected/updated and ported to GHC? Maybe a tool could even be created that automates the interoperability of Haskell and arbitrary .NET libraries?

I'm working on a Haskell to .NET bridge for my undergraduate thesis. The goal is to provide access to arbitrary .NET libraries from Haskell, with a convenient syntax. I expect to have something releasable in a few weeks. AndrewA 13:33, 6 October 2007 (UTC)

AMQP Client

It will be great to have a client for the open source protocol AMQ (http://en.wikipedia.org/wiki/Advanced_Message_Queuing_Protocol). This is a new transport protocol, solving problems currently addressed by Java Messaging Service, MQ, Tibco RV, etc. Financial companies such infrastructure to distribute massive amounts of market data (although the protocol can be used for effeciently distributing anything)

Could be improved

Problems with existing solutions, that could be improved.

  • The core HTTP libraries need a lot of work. There is the beginnings of a useful library there, but many http codes are not handled, and there should be simple 'get' and 'head' functionality.
  • Binary serialisation support should be ported to bytestring, and added to the extralibs bundle
  • Support for wider Word values in bytestring.
  • Adding bytestring support to Parsec.
  • Simple process forking/popen, of type String -> IO String, is needed (the implementation should be in base)

If you have code that improves on something in the base libraries, you might consider submitting it to the libraries process, so it can appear in the standard libraries.

Existing libraries (by problem domain)

See the full libraries list.

GUIs

See GUI libraries

High performance string IO

See String libraries

Binary IO

See Binary IO

Compression

See Compressing data

Encryption

See Crypto libraries

Web frameworks

See Web frameworks

XML processing

See XML handling

Database access

See Databases

Libraries to package

Several cool libraries are out there, not yet in hackage / cabal format. Some on the hitlist , that would be great to package up would be:

C libraries

C libraries are often very popular, and cheap to bind to. A good task would be to just write bindings to C libraries, sorted by popularity.

Possible library rankings are provided by:

Retrieved from "https://wiki.haskell.org/index.php?title=Wanted_libraries&oldid=19139"