[m-rev.] for review: better error messages for overloaded types

[Zoltan Somogyi]

On 06-Aug-2001, Fergus Henderson <fjh at cs.mu.OZ.AU> wrote:
> All the code currently in typecheck.m does follow the convention described
> in my previous paragraph.  `report_error_var' and `report_error_arg_var'
> are examples of code which indents things two levels (four spaces).

I guess this is where my confusion was. I thought the mapping was:

	1 level  -> 1 space
	2 levels -> 3 spaces
	3 levels -> 5 spaces
	N levels -> 2N-1 spaces

You are saying that the mapping is

	1 level  -> 2 spaces
	2 levels -> 4 spaces
	3 levels -> 6 spaces
	N levels -> 2N spaces

I have just checked, and the relevant paragraph in notes/coding_standards.html
can be read either way. It should also be updated to recommend the use of
error_util.m. However, since I wrote error_util.m, it reflects my understanding
of the mapping, and not yours.

Zoltan.
--------------------------------------------------------------------------
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
--------------------------------------------------------------------------