[m-rev.] bug fix: deconstructing closures in hlc grades

[Zoltan Somogyi]

On 25-Feb-2002, Fergus Henderson <fjh at cs.mu.OZ.AU> wrote:
> The documentation for the standard library should define the behaviour
> in terms which are independent of any implementation.  It's OK to specify
> what happens for particular back-ends only if this is preceded by an
> implementation-independent definition of the semantics, and the
> back-end-specific behaviour is documented as being specific to this
> implementation (e.g. "For the University of Melbourne Mercury
> implementation, ...").

Here is a new diff for that this documentation.

Zoltan.

Index: deconstruct.m
===================================================================
RCS file: /home/mercury1/repository/mercury/library/deconstruct.m,v
retrieving revision 1.5
diff -u -b -r1.5 deconstruct.m
--- deconstruct.m	24 Feb 2002 11:53:29 -0000	1.5
+++ deconstruct.m	26 Feb 2002 02:13:41 -0000
@@ -87,6 +87,13 @@
 	%	  arguments hidden in the closure.
 	%	- for tuples, the number of elements in the tuple.
 	%	- for arrays, the number of elements in the array.
+	%
+	% Note that in the University of Melbourne implementation, the
+	% implementations of these predicates depart from the above
+	% specification in that with --high-level-code, they do not
+	% deconstruct predicate- and function-valued terms even with
+	% include_details_cc; instead, they return <<predicate>> or
+	% <<function>> (in both cases with arity zero) as appropriate.
 
 	% functor(Data, NonCanon, Functor, Arity)
 	%
--------------------------------------------------------------------------
mercury-reviews mailing list
post:  mercury-reviews at cs.mu.oz.au
administrative address: owner-mercury-reviews at cs.mu.oz.au
unsubscribe: Address: mercury-reviews-request at cs.mu.oz.au Message: unsubscribe
subscribe:   Address: mercury-reviews-request at cs.mu.oz.au Message: subscribe
--------------------------------------------------------------------------