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

[Peter Ross]

On Thu, Dec 06, 2001 at 11:47:05PM +1100, Fergus Henderson wrote:
> On 06-Dec-2001, Peter Ross <peter.ross at miscrit.be> wrote:
> I notice that you've committed some of these changes already...
> could you please either fix them to avoid the problematic references
> to "backends", or back out these changes?
> 

Index: reference_manual.texi
===================================================================
RCS file: /home/mercury1/repository/mercury/doc/reference_manual.texi,v
retrieving revision 1.230
diff -u -r1.230 reference_manual.texi
--- reference_manual.texi	4 Dec 2001 13:51:54 -0000	1.230
+++ reference_manual.texi	6 Dec 2001 13:23:13 -0000
@@ -4815,8 +4815,8 @@
 				       or function as a call to code
 				       written in a different
 				       programming language.
-* Data passing conventions::	       How Mercury types are represented
-				       on the various backends.
+* Data passing conventions::	       How Mercury types are passed to
+				       different languages.
 * Adding foreign declarations::        How to add declarations of
   				       entities in other programming
 				       languages.
@@ -5009,18 +5009,18 @@
 @node Data passing conventions
 @section Data passing conventions
 
-For each backend,
-we explain how to map a Mercury type to a type on the backend.
+For each language,
+we explain how to map a Mercury type to a type in that foreign language.
 We also map the Mercury parameter passing convention
-to the backend parameter passing convention.
+to the language parameter passing convention.
 
 @menu
-* C backend	:: Data passing convention for the C backend.
-* IL backend	:: Data passing convention for the IL backend.
+* C language	:: Data passing convention for the C language.
+* IL language	:: Data passing convention for the IL language.
 @end menu
 
- at node C backend
- at subsection C backend
+ at node C language
+ at subsection C language
 
 For each of the Mercury types @code{int}, @code{float}, @code{char},
 and @code{string}, there is a C typedef for the corresponding type in C:
@@ -5087,8 +5087,8 @@
 Note that the use of these macros is subject to some caveats
 (@pxref{Memory management}).
 
- at node IL backend
- at subsection IL backend
+ at node IL language
+ at subsection IL language
 
 The Mercury types @code{int}, @code{float}, @code{char},
 and @code{string} are mapped to the Common Language Runtime types 
@@ -5254,7 +5254,7 @@
 
 The input and output variables will have C types corresponding
 to their Mercury types, as determined by the rules specified in
- at ref{C backend}.
+ at ref{C language}.
 
 The C code fragment may declare local variables, but it should not
 declare any labels or static variables unless there is also a Mercury
@@ -5462,7 +5462,7 @@
 @c set @code{success} to false (zero).
 
 Each of the head variables will be represented by the Common Language
-Runtime types as specified in @pxref{IL backend}.
+Runtime types as specified in @pxref{IL language}.
 Note that in IL assembler the types
 @samp{System.Int32}, @samp{System.Double}, @samp{System.Char}
 and @samp{System.String}
@@ -6117,7 +6117,7 @@
 @node Passing data to and from C
 @section Passing data to and from C
 
-This section has moved to @pxref{C backend}.
+This section has moved to @pxref{C language}.
 
 @node Using C pointers
 @section Using C pointers

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