edoc(3erl) | Erlang Module Definition | edoc(3erl) |
edoc - EDoc - the Erlang program documentation generator.
EDoc - the Erlang program documentation generator.
This module provides the main user interface to EDoc.
The EDoc documentation data for a module, expressed as an XML document in XMerL format. See the file edoc.dtd for details.
application(Application::atom()) -> ok
Equivalent to application(Application, []).
application(Application::atom(), Options::proplist()) ->
ok
Run EDoc on an application in its default app-directory. See application/3 for details.
See also: application/1.
application(Application::atom(), Dir::filename(),
Options::proplist()) -> ok
Run EDoc on an application located in the specified directory. Tries to automatically set up good defaults. Unless the user specifies otherwise:
See run/2 for details, including options.
See also: application/2.
file(Name::filename()) -> ok
This function is deprecated: See file/2 for details.
Equivalent to file(Name, []).
file(Name::filename(), Options::proplist()) -> ok
This function is deprecated: This is part of the old interface to EDoc and is mainly kept for backwards compatibility. The preferred way of generating documentation is through one of the functions application/2 and files/2.
Reads a source code file and outputs formatted documentation to a corresponding file.
Options:
See get_doc/2 and layout/2 for further options.
For running EDoc from a Makefile or similar, see edoc_run:file/1.
See also: read/2.
files(Files::[filename()]) -> ok
files(Files::[filename()], Options::proplist()) -> ok
Runs EDoc on a given set of source files. See run/2 for details, including options.
get_doc(File::filename()) -> {ModuleName, edoc_module()}
Equivalent to get_doc(File, []).
get_doc(File::filename(), Options::proplist()) ->
{ModuleName, edoc_module()}
Types:
Reads a source code file and extracts EDoc documentation data. Note that without an environment parameter (see get_doc/3), hypertext links may not be correct.
Options:
Specifies a set of EDoc macro definitions. See Inline macro expansion for details.
See read_source/2, read_comments/2 and edoc_lib:get_doc_env/3 for further options.
See also: get_doc/3, layout/2, read/2, run/2, edoc_extract:source/5.
get_doc(File::filename(), Env::edoc_lib:edoc_env(),
Options::proplist()) -> {ModuleName, edoc_module()}
Types:
Like get_doc/2, but for a given environment parameter. Env is an environment created by edoc_lib:get_doc_env/3.
layout(Doc::edoc_module()) -> string()
Equivalent to layout(Doc, []).
layout(Doc::edoc_module(), Options::proplist()) ->
string()
Transforms EDoc module documentation data to text. The default layout creates an HTML document.
Options:
See also: file/2, layout/1, read/2, run/2.
read(File::filename()) -> string()
Equivalent to read(File, []).
read(File::filename(), Options::proplist()) -> string()
Reads and processes a source file and returns the resulting EDoc-text as a string. See get_doc/2 and layout/2 for options.
See also: file/2.
read_comments(File) -> [comment()]
Equivalent to read_comments(File, []).
read_comments(File::filename(), Options::proplist()) ->
[comment()]
Extracts comments from an Erlang source code file. See the module erl_comment_scan(3erl) for details on the representation of comments. Currently, no options are avaliable.
read_source(Name::File) -> [syntaxTree()]
Equivalent to read_source(File, []).
read_source(File::filename(), Options::proplist()) ->
[syntaxTree()]
Reads an Erlang source file and returns the list of "source code form" syntax trees.
Options:
Normally, preprocessing is not necessary for EDoc to work, but if a file contains too exotic definitions or uses of macros, it will not be possible to read it without preprocessing. Note: comments in included files will not be available to EDoc, even with this option enabled.
See also: erl_syntax(3erl), get_doc/2.
run(Files::[filename()], Options::proplist()) -> ok
Runs EDoc on a given set of source files. Note that the doclet plugin module has its own particular options; see the doclet option below.
Also see layout/2 for layout-related options, and get_doc/2 for options related to reading source files.
Options:
Subpackage source files are found by recursively searching for source code files in subdirectories of the known source code root directories. (Also see the source_path option.) Directory names must begin with a lowercase letter and contain only alphanumeric characters and underscore, or they will be ignored. (For example, a subdirectory named test-files will not be searched.)
See also: application/2, files/2.
Richard Carlsson <carlsson.richard@gmail.com>
edoc 0.12 |