[e-lang] Specifying E (was: Returning guards from __getAllegedType: opinions needed)

[Mark S. Miller]

Speaking of the Kernel-E spec, we need one. Kevin, Dean, and I have discussed 
this, and we'd like to use a wiki with some access control with some version 
control. In particular, we'd like to start with traditional wiki open editing. 
But if it gets spammed, we'd like to retroactively impose restrictions then, 
as well as revert to the pre-spammed version at that time.

Ideally, we'd like to use a Waterken-style capwiki, such as Tyler's, Sandro's, 
or possibly Wideword. Their access control is more than sufficient. However, 
AFAIK, none of these remember past versions. If one could easily be enhanced 
to do so, then it should be suitable. Other wikis do integrate in adequate 
version control, but I don't understand their access control. Or perhaps other 
collaborative editing systems might work. Suggestions appreciated.

Starting with E 0.9, I propose that the first two digits label an intended 
language spec, and remaining digits are private to individual implementations 
of the language, and label its implementation versions. Therefore, a future 
E-on-Java 0.9.3 and E-on-CL 0.9.7 would both be attempts at implementing the 
same language, but would otherwise not be obviously comparable.

Regarding the "pragma.syntax" proposal 
<http://www.eros-os.org/pipermail/e-lang/2006-July/011397.html>, I propose we 
modify it to only include these first two digits, as in

     pragma.syntax("0.8")

-- 
Text by me above is hereby placed in the public domain

     Cheers,
     --MarkM