Erlang (programming language)/Tutorials/Modules: Difference between revisions
Jump to navigation
Jump to search
imported>Eric Evers |
imported>Eric Evers |
||
| Line 24: | Line 24: | ||
"utility" is the module created by the file utility.erl | "utility" is the module created by the file utility.erl | ||
utility functions like rotate can be imported else-where with: | utility functions like left rotate can be imported else-where with: | ||
-import(utility). | -import(utility). | ||
so | so we do not need to use the "utility:" prefix. | ||
Importing modules is not generally recommended. This is very similar to python and Java imports. | Importing modules is not generally recommended. This is very similar to python and Java imports. | ||
Revision as of 19:13, 19 April 2008
Erlang modules
Each Erlang_Programming source file
utility.erl
is required to be a separate module. Modules are created with the module statement.
-module(utility). % 1
-export([rotate/0]). % 2
-compile(export_all).
% 3
rotate([H|T]) -> % 4
T ++ [H]. % 5
compile with
c(utility).
run with
utility:rotate([1,2,3]).
and get
[2,3,1].
"utility" is the module created by the file utility.erl
utility functions like left rotate can be imported else-where with:
-import(utility).
so we do not need to use the "utility:" prefix. Importing modules is not generally recommended. This is very similar to python and Java imports.