Applications
Modules

Expand All
Contract All

- System Documentation
  - Installation Guide
  - System Principles
  - Embedded System
  - Getting Started
  - Erlang Reference Manual
  - Programming Examples
  - Efficiency Guide
  - Interoperability Tutorial
  - Design Principles
  - OAM Principles

Application Groups

- Basic
  - compiler
  - erts
  - kernel
  - sasl
  - stdlib
- Database
  - mnesia
  - odbc
- Operation & Maintenance
  - os_mon
  - otp_mibs
  - snmp
- Interface and Communication
  - asn1
  - crypto
  - diameter
  - eldap
  - erl_interface
  - gs
  - inets
  - jinterface
  - megaco
  - public_key
  - ssh
  - ssl
  - wx
  - xmerl
- Tools
  - appmon
  - debugger
  - dialyzer
  - et
  - inviso
  - observer
  - parsetools
  - percept
  - pman
  - reltool
  - runtime_tools
  - syntax_tools
  - toolbar
  - tools
  - tv
  - webtool
- Test
  - common_test
  - eunit
  - test_server
- Documentation
  - edoc
  - erl_docgen
- Object Request Broker & IDL
  - cosEvent
  - cosEventDomain
  - cosFileTransfer
  - cosNotification
  - cosProperty
  - cosTime
  - cosTransactions
  - ic
  - orber
- Miscellaneous
  - hipe

Erlang/OTP R15B02

Welcome to Erlang/OTP, a complete
development environment
for concurrent programming.

Some hints that may get you started faster

- The Erlang language is described in the Erlang Reference Manual. An Erlang tutorial can be found in Getting Started With Erlang.

  In addition to the documentation here Erlang is described in several recent books like:

  - "Erlang Programming" from O'Reilly.
  - "Programming Erlang" from Pragmatic.
  - "Erlang and OTP in Action" from Manning.

  These books are highly recommended as a start for learning Erlang.

- Erlang/OTP is divided into a number of OTP applications. An application normally contains Erlang modules. Some OTP applications, such as the C interface erl_interface, are written in other languages and have no Erlang modules.

- On a Unix system you can view the manual pages from the command line using

          % erl -man <module>

- You can of course use any editor you like to write Erlang programs, but if you use Emacs there exists editing support such as indentation, syntax highlighting, electric commands, module name verification, comment support including paragraph filling, skeletons, tags support and more. See the Tools application for details.

  There is also an Erlang plugin (ErlIDE) for Eclipse if you prefer a more graphical environment. ErlIDE is under active development with new features in almost every release.

- When developing with Erlang/OTP you usually test your programs from the interactive shell (see Getting Started With Erlang) where you can call individual functions. There is also a number of tools available, such as the graphical Debugger and the Observer tool for inspection of system information, ets and mnesia tables etc.

  Also note that there are some shell features like history list (control-p and control-n), in line editing (Emacs key bindings) and module and function name completion (tab) if the module is loaded.

- OpenSource users can ask questions and share experiences on the Erlang questions mailing list.

- Before asking a question you can browse the mailing list archive and read the Frequently Asked Questions.

- Additional information and links of interest for Erlang programmers can be found on the Erlang Open Source site http://www.erlang.org.

Copyright © 1999-2010 Ericsson AB