[e-cvs] cvs commit: e/doc/download/images pedigree.gif pedigree.sdr
markm@eros.cs.jhu.edu
markm@eros.cs.jhu.edu
Fri, 14 Dec 2001 02:46:51 -0500
markm 01/12/14 02:46:51
Modified: doc/download index.html which.html
doc/download/0-8-10delta index.html
doc/download/images pedigree.gif pedigree.sdr
Log:
for the delta3 debut
Revision Changes Path
1.36 +7 -19 e/doc/download/index.html
Index: index.html
===================================================================
RCS file: /cvs/e/doc/download/index.html,v
retrieving revision 1.35
retrieving revision 1.36
diff -u -r1.35 -r1.36
--- index.html 2001/11/17 04:12:38 1.35
+++ index.html 2001/12/14 07:46:51 1.36
@@ -68,31 +68,19 @@
</tr>
<tr>
<td>--></td>
- <td><b><a href="0-8-10gamma/index.html">0.8.10gamma2</a></b>: This is
- the current main release, in which Dean's transformer has been integrated
- into the main development path.</td>
+ <td><b><a href="0-8-10delta/index.html">0.8.10delta3</a></b>: This is
+ the current main release, with MarcS' eDesk and the new Term trees.</td>
</tr>
<tr>
<td> </td>
- <td><a href="0-8-10beta/index.html">0.8.10beta1</a>: Antlr bundled in,
- and used as basis of new Term / Functor trees.</td>
- </tr>
- <tr>
- <td> </td>
- <td><a href="0-8-10alpha/index.html">0.8.10alpha1</a>: The first release
- of E to be distributed (except for 3vat introductions), persistent
- (sort-of), and to support (and confine) locally untrusted code.</td>
+ <td><a href="0-8-10gamma/index.html">0.8.10gamma2</a>: Dean's transformer
+ has been integrated into the main development path, resulting in a
+ significant speedup of E computation.</td>
</tr>
<tr>
<td> </td>
- <td><a href="stl-0-8-9-t-1/index.html">stl-0.8.9t.1a</a>: Dean's transformer
- -- more efficient interpretation, and a first step towards an <i><b><font color="#009000">E</font></b></i>
- compiler. For those working toward compilation.</td>
- </tr>
- <tr>
- <td> </td>
- <td><a href="stl-0-8-9-t/index.html">stl-0.8.9t</a>: Non distributed
- internal release. Major syntax reform. Enhanced eBrowser.</td>
+ <td><a href="0-8-10beta/index.html">0.8.10beta1</a>: Antlr bundled in,
+ and used as basis of new Term / Functor trees.</td>
</tr>
<tr>
<td> </td>
1.40 +22 -38 e/doc/download/which.html
Index: which.html
===================================================================
RCS file: /cvs/e/doc/download/which.html,v
retrieving revision 1.39
retrieving revision 1.40
diff -u -r1.39 -r1.40
--- which.html 2001/11/17 04:12:38 1.39
+++ which.html 2001/12/14 07:46:51 1.40
@@ -52,61 +52,45 @@
<tr>
<td>
<map name="navmap">
- <area shape="rect" coords="80,107,181,137" href="0-8-10gamma/index.html">
- <area shape="rect" coords="85,382,178,414" href="0-8-10alpha/index.html">
- <area shape="rect" coords="252,732,353,761" href="0-8-9-1/index.html">
- <area shape="rect" coords="306,329,395,357" href="stl-0-8-9-t-1/index.html">
- <area shape="rect" coords="95,639,167,670" href="stl-0-8-9-t/index.html">
- <area shape="rect" coords="89,212,172,242" href="0-8-10beta/index.html">
+ <area shape="rect" coords="80,223,181,253" href="0-8-10gamma/index.html">
+ <area shape="rect" coords="252,716,353,745" href="0-8-9-1/index.html">
+ <area shape="rect" coords="87,100,175,127" href="0-8-10delta/index.html">
+ <area shape="rect" coords="89,289,172,319" href="0-8-10beta/index.html">
</map>
- <img src="images/pedigree.gif" border=0 usemap="#navmap" ismap width="420" height="960"></td>
+ <img src="images/pedigree.gif" border=0 usemap="#navmap" ismap width="420" height="939"></td>
<td>
<ul>
<li>
<p>The current release of <b><i><font color="#009000">E</font></i></b>
- is <a href="0-8-10gamma/index.html">0.8.10gamma2</a>, in which
+ is <a href="0-8-10delta/index.html">0.8.10delta3</a>, containing
+ eDesk and Term trees.</p>
+ </li>
+ <li>
+ <p><a href="0-8-10gamma/index.html">0.8.10gamma2</a>, in which
Dean's transformer has been integrated into the main development
path. </p>
</li>
<li>
<p>In <b><i></i></b><a href="0-8-10beta/index.html">0.8.10beta1</a>,
- Antlr bundled in, and ASTs converted to and from the new Term
- / Functor trees. Also, many bug fixes.</p>
- </li>
- <li>
- <p><a href="0-8-10alpha/index.html">0.8.10alpha1</a>, which is
- a hot off the presses first draft of the planned 0.8.10 release.
- Except for those working on E compilation, this is believed
- to be the best version of E. However, since it's new, you may
- run into new problems. If so, please <a href="https://bugs.sieve.net/bugs/?func=addbug&group_id=16380">report
- bugs</a>. <i>Note: if you require CapTP support for 3vat introductions,
- stick with <a href="0-8-9-1/index.html">tl-otc-0.8.9.1b</a>
- for now.</i></p>
- </li>
- <li>
- <p>In <a href="stl-0-8-9-t-1/index.html">stl-0.8.91a</a>, Dean
- has changed the E interpreter to first transform the program
- into an address oriented representation, and then interprets
- that. Those working towards E compilation (Dean, Darius) should
- use this version.</p>
- </li>
- <li>
- <p><a href="stl-0-8-9-t/index.html">stl-0-8-9t</a> is the common
- ancestor of the two current versions, and so is a valuable reference
- for merging their changes into 0.8.10.</p>
+ Antlr bundled in, in anticipation of Term trees. Also, many
+ bug fixes.</p>
</li>
<li>
- <p><a href="0-8-9-1/index.html">tl-otc-0.8.9.1b</a> was the previous
- main version of E, since it was the last/best one with a functioning
- 2vat CapTP system. Users of this should try moving to 0.8.10alpha1
- as soon as they can afford the conversion costs, and if they
- don't currently need support for 3vat introduction. If you need
- help, please contact <a href="mailto:webmaster@erights.org">me</a>.</p>
+ <p><a href="0-8-9-1/index.html">tl-otc-0.8.9.1b</a> was a previous
+ important version of E, since it was the last/best one with
+ a functioning 3vat CapTP system. Users of this should try moving
+ to a more current release as soon as they can afford the conversion
+ costs, and if they don't currently need support for 3vat introduction.
+ If you need help, please contact <a href="mailto:webmaster@erights.org">me</a>.</p>
</li>
</ul>
</td>
</tr>
</table>
+ <p>I only maintain links above for a small number of the most recent releases,
+ and for certain important old versions so long as there's a reason why
+ someone might want to use these. If you wish to obtain a version for which
+ there's no link above, please let <a href="mailto:webmaster@erights.org">me</a> know.</p>
<!-- #EndEditable --></TD>
<TD WIDTH="10%"> </TD>
</TR>
1.5 +75 -10 e/doc/download/0-8-10delta/index.html
Index: index.html
===================================================================
RCS file: /cvs/e/doc/download/0-8-10delta/index.html,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- index.html 2001/12/13 23:55:59 1.4
+++ index.html 2001/12/14 07:46:51 1.5
@@ -136,17 +136,82 @@
<p>As each of these issues are discussed in email or in the bug tracking
system, we will link the paragraphs below to the relevant roots.</p>
<h3>MarcS' eDesk -- Visual POLA for Caplets</h3>
- <ul>
- <li><font color="#FF0000">*** To be written</font></li>
- </ul>
+
+
+ <blockquote>
+ <p>eDesk is a desktop and designed-to-be-secure(*) computing environment
+ built on the E platform, for the installation an running of <i>caplets</i>
+ -- capability-based applets/applications that run with only the authority
+ that has been explicitly given to them.</p>
+ <p>A secure computing architecture means little for its human users unless
+ its security principles are brought out to the user interface in an
+ intuitive, usable, and non-accident prone fashion. The key insight is,
+ once again, Norm's: "<i>A capability combines designation with
+ authority.</i>"</p>
+ <p>Modern user interfaces are the result of billions of dollars of work
+ on the designation problem -- how to tell one thing, designated somehow,
+ to perform some operation of some other thing, also somehow designated.
+ As user interfaces have improved, they have also moved towards more
+ capability-like means of designation, as in the moves from names and
+ clipboards to drag-n-drop.</p>
+ <p>As with Miriam & Ping's <a href="http://www.cs.berkeley.edu/%7Epingster/sec/project/">Interaction
+ Design for End-User Security</a>, the main "trick" of eDesk
+ is to bundle authorization in with these acts of designation. For example,
+ when a capEdit -- our text editor caplet -- requests a file to edit,
+ the file dialog box that pops up enables the user to conventionally
+ designate which file the caplet should edit, but in so doing, in the
+ same act, provides the caplet the authority to do this editing.</p>
+ <hr>
+ <p>(*) eDesk won't really be secure until the "Taming Java"
+ work mentioned below is adequately complete.</p>
+ </blockquote>
<h3>Term Trees, for real this time</h3>
- <ul>
- <li><font color="#FF0000">*** To be written</font></li>
- </ul>
- <h3>Taming Java -- The *.safej files</h3>
- <ul>
- <li><font color="#FF0000">*** To be written</font></li>
- </ul>
+ <blockquote>
+ <p>John McCarthy has said: "<i>XML is just S-Expressions, only ten
+ times as verbose.</i>" This comparison is too kind to XML. What
+ XML, S-Expressions, Antlr ASTs (abstract syntax trees), and Prolog Term
+ trees have in common is that they are simple(*) notations (or surface
+ syntaxes) for simple(*) "practically universal" trees of symbols.
+ These trees are "practically universal" in that many other
+ forms of symbolic data can be mapped into any of these trees.</p>
+ <p>The clearest and most compelling case is the Antlr AST -- these are
+ used to represent the result of parsing anything that can be parsed
+ according to a BNF grammar. This demonstrates that one such universal
+ data structures may have a great multitude of surface syntaxes.</p>
+ <p>Although the Antlr documentation also calls these S-Expressions, and
+ although the Antlr notation for writing them looks like S-Expressions,
+ semantically they are actually most similar to Prolog Term trees. Since
+ Antlr is the system we most desire to interoperate with, as of this
+ release we introduce E's Prolog-like Term trees, with conversions back
+ and forth to Antlr ASTs. We also adopt a Prolog-like surface syntax
+ for our Term trees, as that looks more familiar to the C syntactic tradition.
+ For example, the parsed form of E's</p>
+ <blockquote>
+ <pre>a := "x" * 3</pre>
+ </blockquote>
+ <p>would be written</p>
+ <blockquote>
+ <pre>assignExpr(nounExpr("a"),
+ callExpr(literalExpr("x"),
+ "multiply",
+ literalExpr(3)))</pre>
+ </blockquote>
+ <p>In an E Term, a <i>functor </i>is an identifier or a literal data element.
+ An identifier, like "assignExpr" above, serves the same role
+ as a does a tag name in XML. A literal data element is either a literal
+ character, integer, floating point number, or string, written the same
+ way, and meaning the same thing, as these literal data elements do in
+ E. (This is the same as they do in Java, except that integers are precision
+ unlimited, and floating point numbers are always double precision.)
+ A <i>Term</i> always consists of a functor and zero or more arguments.
+ These arguments are its children, which transitively always form a finite
+ tree. The leaves of the tree are simply Terms with no arguments. For
+ Terms with no arguments, the "<code>()</code>" is optional.</p>
+ <p>We are working towards a quasi-parser for <a href="../../elang/grammar/quasi-terms.html">quasi-literal
+ Term</a> expressions and patterns.</p>
+ <hr>
+ <p>(*) For XML, let's say instead "perceived as simple".</p>
+ </blockquote>
<h1><a name="variants"></a>Variants and Subsets of E</h1>
<p>A complete <font color="#009000"><em><b>E</b></em></font> system is persistent,
distributed, and capability-secure both within and between processes.
1.5 +59 -56 e/doc/download/images/pedigree.gif
Index: pedigree.gif
===================================================================
RCS file: /cvs/e/doc/download/images/pedigree.gif,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
Binary files /tmp/cvsOLfw5J and /tmp/cvsSGqbYj differ
1.5 +51 -49 e/doc/download/images/pedigree.sdr
Index: pedigree.sdr
===================================================================
RCS file: /cvs/e/doc/download/images/pedigree.sdr,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
Binary files /tmp/cvsZ8Z4NK and /tmp/cvsQEkBnl differ