[Swift-commit] r2397 - text/hpdc09submission

noreply at svn.ci.uchicago.edu noreply at svn.ci.uchicago.edu
Mon Jan 5 14:40:02 CST 2009


Author: hategan
Date: 2009-01-05 14:40:02 -0600 (Mon, 05 Jan 2009)
New Revision: 2397

Modified:
   text/hpdc09submission/paper.latex
Log:
some misc changes

Modified: text/hpdc09submission/paper.latex
===================================================================
--- text/hpdc09submission/paper.latex	2009-01-05 20:22:25 UTC (rev 2396)
+++ text/hpdc09submission/paper.latex	2009-01-05 20:40:02 UTC (rev 2397)
@@ -651,21 +651,19 @@
 \subsection{The execution environment for component programs}
 
   A SwiftScript \verb|app| declaration describes how a component
-program is invoked. In order to facilitate a number of interesting
-features, the environment in which programs are executed is tightly
-constrained, substantially more so than in a conventional scripting
-language.
+program is invoked. In order to ensure the correctness of the 
+Swift model, the environment in which programs are executed needs 
+to be constrained.
 
   A program is invoked in its own working directory; in that working
-directory, the program can expect to find all of the files that are
-passed as inputs to the application block; and on exit, it should leave
-all files named by that application block in the same working
-directory. Programs should not make excessive(?) assumptions about
-their working environment; for example, they should not assume that
+directory or one of its subdirectories, the program can expect to find
+all of the files that are passed as inputs to the application block; and
+on exit, it should leave all files named by that application block in
+the same working directory. Applications should also not assume that
 they will be executed on a particular host (to facilitate site
-portability); run in in any particular order with respoect to other
-program invocations in a script (except those implied by datra
-dependency); or that their working directories will or will not be
+portability), run in in any particular order with respect to other
+application invocations in a script (except those implied by data
+dependency), or that their working directories will or will not be
 cleaned up after execution.
 
 Consider the \verb|app| declaration for the \verb|rotate| procedure in
@@ -681,7 +679,7 @@
 will be placed into the application working directory before execution,
 and which files will be expected there after execution. For the above
 declaration, the file mapped to the \verb|input| parameter will be
-placed in the working directory before hand, and the file mapped to
+placed in the working directory beforehand, and the file mapped to
 \verb|output| will be expected there after execution; the input
 parameter \verb|angle| is of primitive type\footnote{need to define
 primitive type earlier on here...} and so no files are staged in for




More information about the Swift-commit mailing list