(>) docs: site

Author: fsantanna

docs/manual/v0.30/ceu-v0.30.md

@@ -175,11 +175,9 @@ <h1 id="overview">Overview<a class="headerlink" href="#overview" title="Permanen
 <ul>
 <li><em>Reactive</em>:    code executes in reactions to events.</li>
 <li><em>Structured</em>:  code uses structured control-flow mechanisms, such as <code>spawn</code>
-                 and <code>await</code> (to create and suspend an activity).</li>
-<li><em>Synchronous</em>: event reactions never overlap and run atomically and to
-                 completion on each activity.
-                 There is no implicit preemption or real parallelism, resulting
-                 in deterministic execution.</li>
+                 and <code>await</code> (to create and suspend lines of execution).</li>
+<li><em>Synchronous</em>: event reactions run atomically and to completion on each line
+                 of execution.</li>
 </ul>
 <!--
 - Event Handling:
@@ -212,12 +210,12 @@ <h1 id="overview">Overview<a class="headerlink" href="#overview" title="Permanen
 
 <p>The synchronous concurrency model of Céu greatly diverges from multithreaded
 and actor-based models (e.g. <em>pthreads</em> and <em>erlang</em>).
-On the one hand, there is no real parallelism at the synchronous kernel of the
-language (i.e., no multi-core execution).
+On the one hand, there is no preemption or real parallelism at the synchronous
+core of the language (i.e., no multi-core execution).
 On the other hand, accesses to shared variables among trails are deterministic
 and do not require synchronization primitives (i.e., <em>locks</em> or
 <em>queues</em>).</p>
-<p>Céu provides static memory management based on lexical scopes and does not
+<p>Céu provides static memory management based on lexical scope and does not
 require a garbage collector.</p>
 <p>Céu integrates safely with C, particularly when manipulating external resources
 (e.g., file handles).
@@ -239,7 +237,7 @@ <h2 id="environments">Environments<a class="headerlink" href="#environments" tit
 -->
 
 <h2 id="synchronous-execution-model">Synchronous Execution Model<a class="headerlink" href="#synchronous-execution-model" title="Permanent link">&para;</a></h2>
-<p>Céu is grounded on a precise definition of <em>logical time</em> (as opposed to
+<p>Céu is grounded on a precise notion of <em>logical time</em> (as opposed to
 <em>physical</em>) as a discrete sequence of input events:
 a sequence because only a single input event is handled at a logical time; 
 discrete because reactions to events are guaranteed to execute in bounded
@@ -350,7 +348,7 @@ <h2 id="parallel-compositions-and-abortion">Parallel Compositions and Abortion<a
 </ol>
 <p>As mentioned in the introduction and emphasized in the execution model, trails
 in parallel do not execute with real parallelism.
-Therefore, it is important to note that parallel compositions provide
+Therefore, it is important to note that parallel compositions support
 <em>awaiting in parallel</em>, rather than <em>executing in parallel</em> (see
 <a href="./statements/#thread">Asynchronous Threads</a> for real parallelism support).
 <!--
@@ -398,10 +396,10 @@ <h2 id="internal-reactions">Internal Reactions<a class="headerlink" href="#inter
     (see <a href="#synchronous-execution-model"><code>rule 2</code></a> for external reactions).
     If an awaking trail emits another internal event, a nested internal
     reaction starts with <code>rule 1</code>.</li>
-<li>The top of stack is popped and the last emitting trail resumes execution
+<li>The top of the stack is popped and the last emitting trail resumes execution
     from its continuation.</li>
 </ol>
-<p>The program and follow illustrates the behavior of internal reactions in Céu:</p>
+<p>The program as follow illustrates the behavior of internal reactions in Céu:</p>
 <pre><code class="ceu">1:  par/and do      // trail 1
 2:      await e;
 3:      emit f;
@@ -474,5 +472,5 @@ <h2 id="internal-reactions">Internal Reactions<a class="headerlink" href="#inter
 
 <!--
 MkDocs version : 0.15.3
-Build Date UTC : 2017-10-29 15:39:37
+Build Date UTC : 2018-03-20 21:39:56
 -->

docs/manual/v0.30/ceu-v0.30.pdf

@@ -210,6 +210,7 @@ <h2 id="keywords">Keywords<a class="headerlink" href="#keywords" title="Permanen
     var             watching        with            yes
 </code></pre>
 
+<p><code>TODO: catch, throw, throws</code></p>
 <h2 id="identifiers">Identifiers<a class="headerlink" href="#identifiers" title="Permanent link">&para;</a></h2>
 <p>Céu uses identifiers to refer to <em>types</em> (<code>ID_type</code>), <em>variables</em> (<code>ID_int</code>),
 <em>vectors</em> (<code>ID_int</code>), <em>pools</em> (<code>ID_int</code>), <em>internal events</em> (<code>ID_int</code>),
@@ -231,7 +232,7 @@ <h2 id="identifiers">Identifiers<a class="headerlink" href="#identifiers" title=
              | s8    | s16    | s32     | s64
              | u8    | u16    | u32     | u64
              | int   | uint   | integer
-             | ssize   | usize )
+             | ssize | usize )
 </code></pre>
 
 <p>Declarations for <a href="./../statements/#abstractions"><code>code</code> and <code>data</code> abstractions</a>
@@ -264,7 +265,7 @@ <h3 id="booleans">Booleans<a class="headerlink" href="#booleans" title="Permanen
 <p>The boolean type has only two possible values: <code>true</code> and <code>false</code>.</p>
 <p>The boolean values <code>on</code> and <code>yes</code> are synonymous to <code>true</code> and can be used
 interchangeably.
-The boolean values <code>off</code> and <code>no</code> are synonymous to `false and can be used
+The boolean values <code>off</code> and <code>no</code> are synonymous to <code>false</code> and can be used
 interchangeably.</p>
 <h3 id="integers">Integers<a class="headerlink" href="#integers" title="Permanent link">&para;</a></h3>
 <p>Céu supports decimal and hexadecimal integers:</p>

docs/manual/v0.30/docs/overview/environment.png

@@ -4,71 +4,71 @@
 
     <url>
      <loc>None/</loc>
-     <lastmod>2017-10-29</lastmod>
+     <lastmod>2018-03-20</lastmod>
      <changefreq>daily</changefreq>
     </url>
 
 
 
     <url>
      <loc>None/lexical_rules/</loc>
-     <lastmod>2017-10-29</lastmod>
+     <lastmod>2018-03-20</lastmod>
      <changefreq>daily</changefreq>
     </url>
 
 
 
     <url>
      <loc>None/types/</loc>
-     <lastmod>2017-10-29</lastmod>
+     <lastmod>2018-03-20</lastmod>
      <changefreq>daily</changefreq>
     </url>
 
 
 
     <url>
      <loc>None/storage_entities/</loc>
-     <lastmod>2017-10-29</lastmod>
+     <lastmod>2018-03-20</lastmod>
      <changefreq>daily</changefreq>
     </url>
 
 
 
     <url>
      <loc>None/statements/</loc>
-     <lastmod>2017-10-29</lastmod>
+     <lastmod>2018-03-20</lastmod>
      <changefreq>daily</changefreq>
     </url>
 
 
 
     <url>
      <loc>None/expressions/</loc>
-     <lastmod>2017-10-29</lastmod>
+     <lastmod>2018-03-20</lastmod>
      <changefreq>daily</changefreq>
     </url>
 
 
 
     <url>
      <loc>None/compilation/</loc>
-     <lastmod>2017-10-29</lastmod>
+     <lastmod>2018-03-20</lastmod>
      <changefreq>daily</changefreq>
     </url>
 
 
 
     <url>
      <loc>None/syntax/</loc>
-     <lastmod>2017-10-29</lastmod>
+     <lastmod>2018-03-20</lastmod>
      <changefreq>daily</changefreq>
     </url>
 
 
 
     <url>
      <loc>None/license/</loc>
-     <lastmod>2017-10-29</lastmod>
+     <lastmod>2018-03-20</lastmod>
      <changefreq>daily</changefreq>
     </url>