<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>Erlang/OTP #release# Documentation</title>
<style type="text/css">
<!--
BODY { background: white }
BODY { font-family: Verdana, Arial, Helvetica, sans-serif }
TH { font-family: Verdana, Arial, Helvetica, sans-serif }
TD { font-family: Verdana, Arial, Helvetica, sans-serif }
P { font-family: Verdana, Arial, Helvetica, sans-serif }
.header { background: #222; color: #fff }
.app { background: #ccc }
-->
</style>
</head>
<body bgcolor=white text="#000000" link="#0000ff" vlink="#ff00ff"
alink="#ff0000">
<center>
<p>
<font size="+1">Welcome to Erlang/OTP, a complete<br>
development environment<br>
for concurrent programming.</font>
</p>
</center>
<br>
<br>
<br>
<p><b>
<font size"+1">
Some hints that may get you started faster
</font>
</b></p>
<ul>
<li>In addition the the documentation here Erlang is described in the book
<a href="http://www.pragprog.com/titles/jaerlang" target="_top">"Programming Erlang"</a>, ISBN 978-1-934356-00-5 which we really recommend as a start.<br/ >
The complete language is also described in the <a href="reference_manual/part_frame.html" target="_top">Erlang Reference Manual</a>. An Erlang tutorial can be found in <a href="getting_started/part_frame.html" target="_top">Getting Started With Erlang</a>.
</li>
<li>Erlang/OTP is divided into a number of OTP <a
href="applications.html">applications</a>. An application normally contains
Erlang <a href="man_index.html">modules</a>. Some OTP applications,
such as the C interface <em>Erl_Interface</em>, are written in other languages and have no Erlang
modules.
<p>
Note that functions that are not imported or prefixed with a module
name belong to the module
<a href="#kernel#/erlang.html" target="_top">erlang</a>
(in the <em>Kernel</em> application).
</p>
<p>
<li>On a Unix system you can view the manual pages from the command
line using
<pre>
% erl -man <module>
</pre>
<p>
<li> 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 <a href="#tools#/index.html"
target="_top">Tools</a> application for details.
<p>
There is also an
<a href="http://erlide.sourceforge.net" target="_top">
Erlang plugin (ErlIde) for Eclipse</a> if you prefer a more graphical
environment. ErlIde is under development and should at the time
of writing this be quite stable and useful.
<li>When developing with Erlang/OTP you usually test your programs
from the interactive shell (see <a href="getting_started/part_frame.html"
target="_top">Getting Started With Erlang</a>) where you can call individual
functions. There is also a number of tools available, such as the graphical <a
href="#debugger#/index.html" target="_top">Debugger</a>, the process
manager <a href="#pman#/index.html" target="_top">Pman</a> and table
viewer <a href="#tv#/index.html" target="_top">TV</a>.
<p> Also note that there are some shell features like history list
(control-p and control-n), inline editing (emacs key bindings) and
module and function name completion (tab) if the module is loaded.
<p>
<li>OpenSource users can ask questions
and share experiences on the <a href="http://www.erlang.org/faq.html"
target="_top">Erlang questions mailing list</a>. <p>
<li>Before asking a question you can browse the <a
href="http://www.erlang.org/pipermail/erlang-questions/"
target="_top">mailing list archive</a> and read the <a
href="http://www.erlang.org/faq/faq.html" target="_top">Frequently
Asked Questions</a>. <p>
<li>Additional information and links of interest for Erlang programmers can be found on the Erlang Open Source site
<a href="http://www.erlang.org/" target="_top">http://www.erlang.org</a>.
<p>
</ul>
</body>
</html>