[Swift-commit] r3893 - text/parco10submission

[noreply at svn.ci.uchicago.edu]

Author: dsk
Date: 2011-01-07 12:05:22 -0600 (Fri, 07 Jan 2011)
New Revision: 3893

Modified:
   text/parco10submission/paper.tex
Log:
changing the fileRef and reference to mapped files


Modified: text/parco10submission/paper.tex
===================================================================
--- text/parco10submission/paper.tex	2011-01-07 17:05:59 UTC (rev 3892)
+++ text/parco10submission/paper.tex	2011-01-07 18:05:22 UTC (rev 3893)
@@ -406,7 +406,7 @@
 
 \emph{Collection types} are provided in Swift by \emph{arrays} and \emph{structures}.
 Structure fields can be of any type, while arrays contain values of only a single type. One
-array type is provided for every atomic type (integer, string, boolean, and file reference).
+array type is provided for every atomic type (integer, string, boolean, and mapped file).
 Arrays use numeric
 indices, but are sparse.
 Both types of collections can contain members of atomic or collection types. Structures contain a finite number of elements. Arrays contain a varying number of elements. Structures and arrays can both recursively reference other structures and arrays in addition to atomic values. Arrays can be nested to provide multi-dimensional indexing.
@@ -418,9 +418,9 @@
 %garbage collection at the "dual" level (i.e., clean temp files) as well as remove unused futures from memory}
 % Mike: I mentioned GC as it pertains to structures and arrays: since swift is single-assignment, structures and arrays can never get de-referenced and thus dont need to be GC'ed - *I think*. But I can see that internal objects like futures should be, and given that they dont, its best to steer clear of this issue for now.
 
-Variables that are declared to be file references
+Variables that are declared to be mapped files
 are associated with a \emph{mapper}, which defines (often through a dynamic lookup process) the
-data files that are to be mapped to the variable. Array and structure elements that are declared to be file references are similarly mapped.
+data files that are to be mapped to the variable. Array and structure elements that are declared to be mapped files are similarly mapped.
 
 Mapped type and collection 
 type variable declarations can be annotated with a
@@ -744,13 +744,13 @@
 Types are used to structure data, to aid in debugging and program
 correctness and to influence how Swift interacts with data.
 
-The \verb|image| type declared in previous examples is a \emph{file reference
-type} which we refer to as a \emph{fileRef}. fileRef types indicate that variable refers to a
+The \verb|image| type declared in previous examples is a \emph{mapped file
+type} which we refer to as a \emph{mapped file}. The mapped file type indicates that variable refers to a
 single file, and that no further structural information about the file is exposed at the Swift level.
 
 Arrays have been mentioned above, in the arrays section. A code block
 may be applied to each element of an array using \verb|foreach|; or
-individual elements may be references using \verb|[]| notation.
+individual elements may be mapped files using \verb|[]| notation.
 
 There are a number of primitive types: \verb|int|, \verb|string|,
 \verb|float|, \verb|boolean|, which represent integers, strings,