[m-dev.] For review: Using MR_TypeCtorInfo for generated type_ctor_infos

[Zoltan Somogyi]

> who knows about this stuff comment on whether it was fine as it was, or 
> whether it should be changed?  Of course if it should be changed, no doubt 
> the `multi_string_const' entry should be changed as well.
> 
> Index: compiler/llds.m
> ===================================================================
> RCS file: /home/mercury1/repository/mercury/compiler/llds.m,v
> retrieving revision 1.244
> diff -u -r1.244 llds.m
> --- llds.m      1999/07/13 08:53:05     1.244
> +++ llds.m      1999/08/05 07:33:43
> @@ -1006,7 +1006,7 @@
>  llds__const_type(false, bool).
>  llds__const_type(int_const(_), integer).
>  llds__const_type(float_const(_), float).
> -llds__const_type(string_const(_), data_ptr).
> +llds__const_type(string_const(_), string).
>  llds__const_type(multi_string_const(_, _), data_ptr).
>  llds__const_type(code_addr_const(_), code_ptr).
>  llds__const_type(data_addr_const(_), data_ptr).

I'd leave it as it was.

> 1.  Go with the full change (all type_ctor_info structures use the 
> MR_TypeCtorInfo type, whether hand-defined or compiler-generated) with the 
> above fix for the warnings.

If they get rid of all warnings, then by all means please do this.

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