[Swift-commit] r3882 - text/parco10submission

[noreply at svn.ci.uchicago.edu]

Author: hategan
Date: 2011-01-06 17:34:54 -0600 (Thu, 06 Jan 2011)
New Revision: 3882

Modified:
   text/parco10submission/paper.tex
Log:
made a comment on garbage collection and changed one instance of "composite type" to "collection type"

Modified: text/parco10submission/paper.tex
===================================================================
--- text/parco10submission/paper.tex	2011-01-06 23:19:27 UTC (rev 3881)
+++ text/parco10submission/paper.tex	2011-01-06 23:34:54 UTC (rev 3882)
@@ -7,6 +7,7 @@
 \usepackage{framed}
 \newcommand{\katznote}[1]{ {\textcolor{cyan}   { ***Dan:   #1 }}}
 \newcommand{\mikenote}[1]{ {\textcolor{red}   { ***Mike:   #1 }}}
+\newcommand{\mihaelnote}[1]{ {\textcolor{green}   { ***Mihael:   #1 }}}
 \newcommand{\hide}[1]{ {{}}}
 
 \definecolor{shadecolor}{RGB}{240,255,200}
@@ -391,12 +392,14 @@
 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.
 
 Due to the dynamic, highly parallel nature of Swift, its arrays have no notion of size. Array elements can be set as a script's execution progresses. The number of elements set increases monotonically. An array is considered ``closed'' when no further statements that set an element of the array can be executed. This state is recognized at run time by information obtained from compile-time analysis of the script's call graph. Also, since all data elements have single-assignment semantics, no garbage collection issues arise. \katznote{does this follow? garbage collection removed variables that are no longer needed - I don't see how single assignment helps here.}
+\mihaelnote{I think we should not mention the garbage collection issue. In fact, we don't and we should implement
+garbage collection at the "dual" level (i.e., clean temp files) as well as remove unused futures from memory}
 
 Variables that are declared to be file references
 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.
 
-Mapped type and composite \katznote{I don't know what composite means here}
+Mapped type and collection \katznote{I don't know what composite means here}\mihaelnote{changed "composite type" to "collection type" as introduced earlier}
 type variable declarations can be annotated with a
 \emph{mapping} descriptor that specify the file(s) that are to be mapped to the Swift data element(s).