[m-dev.] for review: add MC++ implementation of library and runtime

[Zoltan Somogyi]

On 06-Dec-2000, Fergus Henderson <fjh at cs.mu.OZ.AU> wrote:
> I think that's a fine solution.

Here is the diff.

compiler/det_report.m:
	Do not report "determinism declaration could be tighter" warnings
	for compiler-generated procedures.

Zoltan.

Index: det_report.m
===================================================================
RCS file: /home/mercury1/repository/mercury/compiler/det_report.m,v
retrieving revision 1.64
diff -u -b -r1.64 det_report.m
--- det_report.m	2000/11/23 04:32:17	1.64
+++ det_report.m	2000/12/06 05:47:12
@@ -125,7 +125,7 @@
 :- import_module prog_out. 
 :- import_module hlds_data, type_util, mode_util, inst_match.
 :- import_module hlds_out, mercury_to_mercury.
-:- import_module passes_aux.
+:- import_module code_util, passes_aux.
 :- import_module globals, options.
 
 :- import_module term, varset.
@@ -178,7 +178,15 @@
 				% This is similar to the reason we don't
 				% report warnings for lambda expressions.
 				{ \+ check_marker(Markers,
-					class_instance_method) }
+					class_instance_method) },
+
+				% Don't report warnings for compiler-generated
+				% Unify, Compare or Index procedures, since the
+				% user has no way to shut these up. These can
+				% happen for the Unify pred for the unit type,
+				% if such types are not boxed (as they are not
+				% boxed for the IL backend).
+				{ \+ code_util__compiler_generated(PredInfo0) }
 			->
 				{ Message = "  warning: determinism declaration could be tighter.\n" },
 				report_determinism_problem(PredId,
--------------------------------------------------------------------------
mercury-developers mailing list
Post messages to:       mercury-developers at cs.mu.oz.au
Administrative Queries: owner-mercury-developers at cs.mu.oz.au
Subscriptions:          mercury-developers-request at cs.mu.oz.au
--------------------------------------------------------------------------