Files
mercury/doc
Zoltan Somogyi 7f6bb059a0 Update comments in file_names.m.
compiler/file_names.m:
    Delete now-obsolete comments. Move their still-relevant parts
    next to the entity that they apply to.

    List the string form, if any, of each enum representing an extension.

    Explain the meaning of _gs, _ngs and _opt suffixes.

    Delete obsolete commented-out code.

    Delete an obsolete, unused type definition.

compiler/options.m:
doc/user_guide.texi:
    Fix two bugs that a comment that this diff pointed to.

    First, since 2017, the --dump-hlds option has output C code
    only if the target language is C, but the documentation
    of that option did not mention this. Fix this omission.

    Second, ever since we split .mh and .mih files, the header
    part of MLDS dumps in C form were output to .mih_dump file.
    However, the documentation of the --dump-hlds  option said that
    it was output to a .h_dump file. Fix this as well.
2023-07-06 02:29:03 +02:00
..
2023-01-02 15:54:22 +11:00
2019-05-28 15:54:45 +10:00
2023-02-14 17:25:08 +11:00

This directory contains the source for

	The Mercury user's guide
	The Mercury language reference manual
	The Mercury library reference manual
	The Prolog to Mercury transition guide
	The Mercury frequently asked questions list

The master copy of each document is stored in texinfo format, from which
the info, dvi and html versions are derived automatically.

You can create postscript versions from either the dvi or html versions.
Due to the large spacing in texinfo-generated dvi files, the postscript file
generated from the html (manually via a browser such as xmosaic) will be
considerably shorter than the one derived from the dvi file.

The source for the Mercury library reference manual is generated automatically
from the library source files themselves.