Next: Warnings about missing order, Previous: Warnings about style issues with predicates, Up: Warnings about programming style [Contents][Index]
--no-warn-redundant-codeDo not warn about redundant constructs in Mercury code. (One example is importing a module more than once.)
--warn-ite-instead-of-switch--inform-ite-instead-of-switchGenerate warnings for if-then-elses that could be replaced by switches.
--warn-incomplete-switch--inform-incomplete-switchGenerate warnings for switches that do not cover all the function symbols that the switched-on variable could be bound to.
--warn-incomplete-switch-threshold N--inform-incomplete-switch-threshold NHave the ‘--warn-incomplete-switch’ option generate its messages only for switches that do cover at least ‘N’% of the function symbols that the switched-on variable could be bound to.
--warn-duplicate-callsWarn about multiple calls to a predicate or function with the same input arguments.
--no-warn-redundant-coerceDo not warn about redundant type coercions, which occur when the type
of the result of the coerce expression is the same as the type
of its argument.
--no-warn-requested-by-codeDo not generate warnings that are specifically requested by the code
being compiled, such as require_switch_arms_in_type_order
pragmas.
--no-warn-requested-by-optionDo not generate warnings that are specifically requested by compiler options, such as “–enable-termination”.
--no-warn-state-var-shadowingDo not warn about one state variable shadowing another.
--no-warn-unneeded-initial-statevarsDo not warn about state variables in clause heads that could be ordinary variables.
--no-warn-unneeded-initial-statevars-lambdaDo not warn about state variables in the heads of lambda expressions that could be ordinary variables.
--warn-implicit-stream-callsWarn about calls to I/O predicates that could take explicit stream arguments, but do not do so.
--warn-unknown-format-callsWarn about calls to string.format, io.format or
stream.string_writer.format for which the compiler cannot tell
whether there are any mismatches between the format string and the
supplied values.
--warn-suspicious-foreign-codeWarn about possible errors in the bodies of foreign code pragmas.
Note that since the compiler’s ability to parse foreign language code is limited, some warnings reported by this option may be spurious, and some actual errors may not be detected at all.
--warn-suspicious-foreign-procsWarn about possible errors in the bodies of foreign_proc pragmas. When
enabled, the compiler attempts to determine whether the success
indicator for a foreign procedure is correctly set, and whether the
foreign procedure body contains operations that it should not contain,
such as return statements in a C foreign procedure.
Note that since the compiler’s ability to parse foreign language code is limited, some warnings reported by this option may be spurious, and some actual errors may not be detected at all.
Next: Warnings about missing order, Previous: Warnings about style issues with predicates, Up: Warnings about programming style [Contents][Index]