[Swift-commit] r3892 - text/parco10submission

[noreply at svn.ci.uchicago.edu]

Author: wilde
Date: 2011-01-07 11:05:59 -0600 (Fri, 07 Jan 2011)
New Revision: 3892

Modified:
   text/parco10submission/paper.tex
Log:
Minor edits in intro. Also changed PERL to Perl per Glen.

Modified: text/parco10submission/paper.tex
===================================================================
--- text/parco10submission/paper.tex	2011-01-07 16:48:49 UTC (rev 3891)
+++ text/parco10submission/paper.tex	2011-01-07 17:05:59 UTC (rev 3892)
@@ -120,9 +120,9 @@
 %It is intended to serve as a higher level framework for composing the interaction of
 %concurrently executing programs (even parallel ones) and scripts
 %written in other scripting languages.
-Swift %is a higher-level language that
+Unlike most other scripting languages, Swift %is a higher-level language that
 focuses not on the details of executing sequences or
-pipelines of scripts and programs (even parallel ones), but rather on the issues that arise
+pipelines of scripts and programs, but rather on the issues that arise
 from the concurrent execution, composition, and coordination of many independent computational tasks at
 large scale.
 %
@@ -177,7 +177,7 @@
 % be and the monentary lack of libraries is independent of the language. Most functional languages are simpler
 % than Swift.
 
-Swift can execute scripts that perform tens of thousands of program
+Swift can execute scripts that perform hundreds of thousands of program
 invocations on highly parallel resources, and handle the unreliable
 and dynamic aspects of wide-area distributed resources. Such issues are handled by Swift's runtime system, and are not manifest in the user's scripts.
 The exact number of processing units available on such shared resources
@@ -218,7 +218,7 @@
 
 In order to achieve automatic
 parallelization, Swift is based on the synchronization construct of \emph{futures}~\cite{Futures}, which
-can result in abundant parallelism. Every Swift variable (including every members of structures and arrays) is a future.
+can enable large-scale parallelism. Every Swift variable (including all members of structures and arrays) is a future.
 Using a futures-based evaluation strategy has an enormous benefit:
 automatic parallelization is achieved without the need for
 dependency analysis, which would significantly complicate the Swift implementation.
@@ -1122,7 +1122,7 @@
 
 Clustering requires very little additional support on the remote site, while
 the coasters framework requires an active component on the
-head node (in Java) and on the worker nodes (in PERL) as well as
+head node (in Java) and on the worker nodes (in Perl) as well as
 additional network connectivity within a site. In practice, the
 automatic deployment and execution of these components can be
 difficult on a number sites.