[m-rev.] Re: [m-dev.] for discussion: pragma foreign_import

[Peter Ross]

On Wed, Dec 05, 2001 at 05:57:07PM +1100, Fergus Henderson wrote:
> > Index: reference_manual.texi
> > ===================================================================
> > RCS file: /home/mercury1/repository/mercury/doc/reference_manual.texi,v
> > retrieving revision 1.229
> > diff -u -r1.229 reference_manual.texi
> > --- reference_manual.texi	4 Dec 2001 11:11:59 -0000	1.229
> > +++ reference_manual.texi	4 Dec 2001 13:43:47 -0000
> > @@ -5009,7 +5009,10 @@
> >  @node Data passing conventions
> >  @section Data passing conventions
> >  
> > -Each backend will have its own conventions for passing data.
> > +For each backend,
> > +we explain how to map a Mercury type to a type on the backend.
> > +We also map the Mercury parameter passing convention
> > +to the backend parameter passing convention.
> 
> s/backend/back-end/g
> 
> Also the conventions should be language-specific,
> not back-end specific.
> 
I am not so sure about this.

Why should the Managed C++ convention be different to the C convention?
MC++ is just a superset of C.  It is different because we do different
things on the different backends.

The language specific convention is simply a translation of the backend
convention to the terms in your programming language.  That is why the
section on interfacing with IL refers to the `IL Backend' section with
notes on how to map the CLR types onto IL type names.  It should be
something similar for C# and MC++, when they are documented.
--------------------------------------------------------------------------
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
--------------------------------------------------------------------------