aboutsummaryrefslogtreecommitdiffstats
path: root/lib/edoc/src/edoc.erl
AgeCommit message (Collapse)Author
2015-03-12edoc: Correct documentationHans Bolinder
Substitute references to edoc_lib:get_doc_env/3 for references to edoc_lib:get_doc_env/4.
2015-01-16[edoc] remove functionality related to packagesVlad Dumitrescu
The 'subpackages' option is left, since some projects use recursive source directories.
2014-06-26edoc, syntax_tools: Don't fail on invalid UTF-8Hans Bolinder
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.
2013-02-20Merge branch 'hb/edoc/bug_fix/OTP-10866'Hans Bolinder
* hb/edoc/bug_fix/OTP-10866: [edoc] Fix a bug involving a type declaration and a comment
2013-02-19[edoc] Fix a bug involving a type declaration and a commentHans Bolinder
2013-02-19Use ~ts for filenamesHans Bolinder
2013-01-09edoc: Remove support for packagesBjörn Gustavsson
2013-01-02[edoc] Introduce Unicode support for source filesHans Bolinder
2011-09-25updated author e-mailRichard Carlsson
2011-08-04eliminate warnings about unused importsRichard Carlsson
2011-08-04removed CVS-keywords from source filesRichard Carlsson
2011-08-04synchronized with edoc development versionRichard Carlsson
2011-03-10Make Erlang specifications and types available in EDocHans Bolinder
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.
2010-09-15edoc: Do not auto-import error/1Tuncer Ayaz
Resolve name clash with auto-imported BIF error/1.
2009-11-20The R13B03 release.OTP_R13B03Erlang/OTP