[m-rev.] for review: document 64-bit integer types in the reference manual

Peter Wang novalazy at gmail.com
Mon Feb 19 09:49:17 AEDT 2018


On Sat, 17 Feb 2018 20:38:18 -0500 (EST), Julien Fischer <jfischer at opturion.com> wrote:
> 
> For review by anyone.
> 
> --------------------
> 
> Document 64-bit integer types in the reference manual.
> 
> doc/reference_manual.texi:
>       Uncomment or add documentation for the two 64-bit integer types.
> 
> Julien.

> @@ -7237,6 +7239,16 @@ Omitting the call to @code{MR_word_to_float} in the above example would yield
>   incorrect results for implementations where @samp{sizeof(MR_Float)} is greater
>   than @samp{sizeof(MR_Word)}.
> 
> +Similarly, the implementation provides the macros @code{MR_word_to_int64} and
> + at code{MR_word_to_uint64} for converting values of type @code{MR_Word} to ones
> +of type @code{int64_t} or @code{uint64_t} respectively, and the macros
> + at code{MR_int64_to_word} and @code{MR_uint64_to_word} for converting values of
> +type @code{int64_t} or @code{uint64_t} respectively to ones of type
> + at code{MR_Word}.
> +These macros must be used to perform these conversions since for some Mercury
> +implementations @samp{sizeof(int64_t)} or @samp{sizeof(uint64_t)} is greater
> +than @samp{sizeof(MR_Word)}.

and .. are greater than

> 
> -Note that since Java lacks unsigned integer types, Mercury's @code{uint} type
> -corresponds to the Java type @code{int}.
> +Note that since Java lacks unsigned integer types, Mercury's unsigned integer
> +type correspond to signed integer types in Java.

types correspond

That's fine.

Peter


More information about the reviews mailing list