| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Fix mistakes found by 'xmllint'.
|
|
|
|
Substitute references to edoc_lib:get_doc_env/3 for references to
edoc_lib:get_doc_env/4.
|
|
The 'subpackages' option is left, since some projects use recursive
source directories.
|
|
As a temporary measure to ease the transition to default UTF-8
encoding, automatically fall back to the Latin-1 encoding (without any
warnings; the Erlang Compiler will emit a proper warning).
The intention is to remove this workaround in OTP 18 or 19.
|
|
* hb/edoc/bug_fix/OTP-10866:
[edoc] Fix a bug involving a type declaration and a comment
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
It is now possible to use Erlang specifications and types in EDoc
documentation. Erlang specifications and types will be used unless
there is also a function specification (@spec) or a type alias (@type)
with the same name. In the current implementation the placement of
-spec matters: it should be placed where the @spec would otherwise
have been placed.
Not all Erlang types are included in the documentation, but only those
exported by some export_type declaration or used by some documented
Erlang specification (-spec).
There is currently no support for overloaded Erlang specifications.
The syntax definitions of EDoc have been augmented to cope with most
of the Erlang types. (But we recommend that Erlang types should be
used instead.)
edoc:read_source() takes one new option, report_missing_types.
edoc_layout:module() takes one new option, pretty_printer.
|
|
Resolve name clash with auto-imported BIF error/1.
|
|
|
