aboutsummaryrefslogtreecommitdiffstats
path: root/lib/edoc/src/edoc_parser.yrl
AgeCommit message (Collapse)Author
2016-11-23Make use of the Header feature in yeccRichard Carlsson
2016-11-23Update EDoc license headers to dual Apache2/LGPLRichard Carlsson
This makes it clear that Apache 2.0 applies, without dropping the old LGPL licensing, and makes all the EDoc file headers look the same as upstream.
2016-06-09Remove support for '...' in Maps typesHans Bolinder
It is possible that '...' is added later (OTP 20.0), but for now we are not sure of all details.
2016-06-08edoc: Fix new Maps syntaxHans Bolinder
2015-04-30edoc: Use module erl_annoHans Bolinder
2015-01-16[edoc] remove functionality related to packagesVlad Dumitrescu
The 'subpackages' option is left, since some projects use recursive source directories.
2014-01-28edoc,syntax_tools: Teach Map understandingBjörn-Egil Dahlberg
2013-04-19Remove the "coding: utf-8" comment from all Erlang source filesHans Bolinder
2013-02-19Use ~ts for filenamesHans Bolinder
2013-01-09edoc: Remove support for packagesBjörn Gustavsson
2013-01-09Prepare OTP files for Unicode as default encodingHans Bolinder
2012-08-22Fix an issue with parentheses and separate values of union typesHans Bolinder
Since EDoc 0.7.7 (R14B02) separate values of union types can be annotated. However, the parser has hitherto chosen not to add the necessary parentheses due to backwards compatibility. From this release on code traversing the output of edoc_parser needs to take care of parentheses around separate values of union types. Examples of such code are layout modules and doclet modules. The following example shows annotated values of a union type: -type t() :: (Name1 :: atom()) | (Name2 :: integer()).
2011-09-25removed some never-matching clauses reported by dialyzerRichard Carlsson
2011-09-25updated author e-mailRichard 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-11-15Fix various dialyzer warningsKostis Sagonas
Add appropriate specs to shut off dialyzer's no_return warnings and also fix an erroneous use of lists:concat/1 instead of lists:append/1.
2009-11-20The R13B03 release.OTP_R13B03Erlang/OTP