6 Erlang Libraries
The full library descriptions are included with the open-source distribution and also on line. The highlights are:
SASL, EVA, INETS and SNMP provide Operations- and maintenance-related functionality: release handling, alarm and event handling, administration via web browser and SNMP.
ORBER, CosEvent, CosTransactions and IC contain support for everything CORBA related.
Mnesia and Mnemosyne provide a real-time distributed database which can be both in-RAM and on-disk. There is also a standard ODBC client driver.
There is an ASN.1 compiler which produces Erlang code.
A rich collection of modules provides everything from string, list and regular expression manipulation to random number generation and calendar lookups.
gen_server, gen_fsm, and supervision trees provide standard ways of implementing client/server subsystems, state machines and supervised fault-tolerant systems.
GUI and Graphics
wx, gs and webtool provide ways to build a gui.
Among other things, there are also HTTP, SSH and FTP servers.
Linked lists are a fundamental part of Erlang, as are tuples. The other standard data structures are:
|sets||sets, i.e. a collection of unique elements.|
|gb_sets||sets, but based on a general balanced data structure|
|gb_tree||a general balanced tree|
|dict||maps, also called associative arrays|
|ets||hash tables and ordered sets (trees), stored outside the process|
|dets||on-disk hash tables|
(Beware: the less frequently used modules ordset and orddict are merely ordered lists, and thus have O(n) for common operations such as insert.)
Johan Bevemyr wrote one which works for unix machines. The code is freely available at the contributions area as serial-1.0.
There have been discussions on the mailing list about writing a more general driver which also works on windows machines. Nothing much has come of this (lack of interest?).
There are several.
For those who like glade, the GTK interface builder, there's a binding to GTK which is tightly coupled to glade. For the bare-metal types, there's some interesting work to directly access the X protocol.
This takes more work and patience than most people have. Kent Boortz described many of the hurdles on the mailing list.
There are other ways to spread your code, including distributing it from your own website or starting a project at a code hosting site. github is quite popular with Erlang developers.