application(Args::args())->no_return()
Calls edoc:application/3 with the corresponding arguments. The strings in the list are parsed as
Erlang constant terms. The list can be either [App], [App,Options] or [App,Dir,Options]. In the
first case edoc:application/1 is called instead; in the second case, edoc:application/2 is called.
The function call never returns; instead, the emulator is automatically terminated when the call
has completed, signalling success or failure to the operating system.
file(Args::args())->no_return()Thisfunctionisdeprecated: 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/1 and files/1.
Calls edoc:file/2 with the corresponding arguments. The strings in the list are parsed as Erlang
constant terms. The list can be either [File] or [File,Options]. In the first case, an empty list
of options is passed to edoc:file/2.
The following is an example of typical usage in a Makefile:
$(DOCDIR)/%.html:%.erl
erl -noshell -run edoc_run file '"$<"' '[{dir,"$(DOCDIR)"}]' \
-s init stop
The function call never returns; instead, the emulator is automatically terminated when the call
has completed, signalling success or failure to the operating system.
files(Args::args())->no_return()
Calls edoc:files/2 with the corresponding arguments. The strings in the list are parsed as Erlang
constant terms. The list can be either [Files] or [Files,Options]. In the first case,
edoc:files/1 is called instead.
The function call never returns; instead, the emulator is automatically terminated when the call
has completed, signalling success or failure to the operating system.