mirror of
https://github.com/Mercury-Language/mercury.git
synced 2026-04-15 17:33:38 +00:00
807d1d8671
compiler/hlds_out_util.m:
When setting up hlds_out_info, the structure threaded through
all the code that does HLDS dumps, include in it not the raw value
of the --hlds-dump-options option, but a structure derived from it,
which contains a vector of boolean flags.
compiler/hlds_out_goal.m:
compiler/hlds_out_module.m:
compiler/hlds_out_pred.m:
compiler/hlds_out_type_table.m:
compiler/hlds_out_typeclass_table.m:
Instead of testing whether a particular character occurs in the value
of --hlds-dump-options, test the boolean flag that corresponds to that
character. Selecting that boolean flag using its field name makes
this test more readable, since e.g. "DumpOptions ^ dump_predicates = yes"
is a lot clearer than "string.contains_char(DumpOptions, 'x')".
It should also be very slightly faster.
compiler/intermod.m:
Conform to the changes above.
doc/user_guide.texi:
Fix some minor issues in the documentation of the --hlds-dump-options
option that were revealed by work on the changes above.
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.