[m-rev.] for review: data passing convention documentation

[Peter Ross]

On Thu, Dec 06, 2001 at 07:24:03PM +1100, Fergus Henderson wrote:
> On 03-Dec-2001, Peter Ross <peter.ross at miscrit.be> wrote:
> > +The Mercury types @code{int}, @code{float}, @code{char},
> > +and @code{string} are mapped to the Common Language Runtime types 
> > + at code{System.Int32}, @code{System.Double}, @code{System.Char} and
> > + at code{System.String} respectively.
> > +
> > +Mercury variables which are polymorphically typed (e.g. whose type is a 
> > +type variables) will be passed as @code{System.Object} while all other
> > +Mercury variables are passed as @code{System.Object[]}.
> > +This mapping is subject to change and you should try to avoid writing
> > +code that relies heavily upon a particular representation of Mercury
> > +terms.
> 
> The documentation here should explain both the --high-level-data
> and --no-high-level-data case, rather than assuming --no-high-level-data.
> 
Since you designed and implemented the high-level-data representation, I
would suggest that you are better placed to document it than me.  BTW
does it even work yet?

However see my other mail which contains a more general discussion about
foreign language interfacing?  I think that we need to do some more
thinking and design work on the interface first.
--------------------------------------------------------------------------
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
--------------------------------------------------------------------------