User:ThomasLeonard - Revision history

ThomasLeonard: SAM

2011-06-29T08:11:47Z

SAM

New page

I'm using E for two separate projects:

* At [http://www.it-innovation.soton.ac.uk/ IT Innovation], for some of our experimental work on service oriented architectures.
* At [http://0install.net/ebox.html 0install.net], as a demonstrator showing how to use 0install to run sandboxed applications with distributed dependencies.

I've also made [[SAM]] - a tool for modelling the way capabilities can propagate in capability systems.

== Branches ==

I publish my patches to [http://gitorious.org/~tal-itinnov/repo-roscidus/it-innovation my E Git repository]. The '''next''' branch generally contains things I consider ready for merging into the E svn repository.

Other patches/branches:

* [http://www.eros-os.org/pipermail/e-lang/2010-October/013648.html Make CapTP shutdown when its vat is shutdown] (on next).
* [http://www.eros-os.org/pipermail/e-lang/2010-September/013620.html Split Scope] into Scope (internal data structure for the E interpreter, including local variables, etc) and EEnv (simpler structure exposed to E code, replacing safeScope, etc). This avoids the need to tame access to these objects and hopefully makes the code easier to read.
* Various possible optimisations are on the '''compiler''' branch (these mostly have only a small benefit or don't work fully; otherwise I push them to next). These optimisations work for both the current E interpreter and for a possible future E compiler. There is also a very old wip-compiler branch that actually does compile E to JVM bytecode. However, it turned out that the major performance problems were elsewhere.

ThomasLeonard at 12:07, 9 November 2010

2010-11-09T12:07:56Z

←Older revision		Revision as of 12:07, 9 November 2010
Line 2:		Line 2:

	* At [http://www.it-innovation.soton.ac.uk/ IT Innovation], for some of our experimental work on service oriented architectures.		* At [http://www.it-innovation.soton.ac.uk/ IT Innovation], for some of our experimental work on service oriented architectures.
-	* At [http://0install.net/ebox.html 0install.net], as a demonstrator showing how to use 0install to run sandboxed applications with distributed ~~dependency handling~~.	+	* At [http://0install.net/ebox.html 0install.net], as a demonstrator showing how to use 0install to run sandboxed applications with distributed dependencies.

	== Branches ==		== Branches ==

ThomasLeonard at 12:02, 9 November 2010

2010-11-09T12:02:11Z

←Older revision		Revision as of 12:02, 9 November 2010
Line 10:		Line 10:
	Other patches/branches:		Other patches/branches:

-	* [http://www.eros-os.org/pipermail/e-lang/2010-October/~~013647~~.html Make CapTP shutdown when its vat is shutdown] (on next).	+	* [http://www.eros-os.org/pipermail/e-lang/2010-October/013648.html Make CapTP shutdown when its vat is shutdown] (on next).
	* [http://www.eros-os.org/pipermail/e-lang/2010-September/013620.html Split Scope] into Scope (internal data structure for the E interpreter, including local variables, etc) and EEnv (simpler structure exposed to E code, replacing safeScope, etc). This avoids the need to tame access to these objects and hopefully makes the code easier to read.		* [http://www.eros-os.org/pipermail/e-lang/2010-September/013620.html Split Scope] into Scope (internal data structure for the E interpreter, including local variables, etc) and EEnv (simpler structure exposed to E code, replacing safeScope, etc). This avoids the need to tame access to these objects and hopefully makes the code easier to read.
	* Various possible optimisations are on the '''compiler''' branch (these mostly have only a small benefit or don't work fully; otherwise I push them to next). These optimisations work for both the current E interpreter and for a possible future E compiler. There is also a very old wip-compiler branch that actually does compile E to JVM bytecode. However, it turned out that the major performance problems were elsewhere.		* Various possible optimisations are on the '''compiler''' branch (these mostly have only a small benefit or don't work fully; otherwise I push them to next). These optimisations work for both the current E interpreter and for a possible future E compiler. There is also a very old wip-compiler branch that actually does compile E to JVM bytecode. However, it turned out that the major performance problems were elsewhere.

ThomasLeonard at 11:57, 9 November 2010

2010-11-09T11:57:40Z

←Older revision		Revision as of 11:57, 9 November 2010
Line 10:		Line 10:
	Other patches/branches:		Other patches/branches:

-	* Make CapTP shutdown when its vat is shutdown (on next)	+	* [http://www.eros-os.org/pipermail/e-lang/2010-October/013647.html Make CapTP shutdown when its vat is shutdown] (on next).
-	* ~~Various possible optimisations are on the '''compiler''' branch (these mostly have only a small benefit or don't work fully; otherwise I push them to next)~~	+	* [http://www.eros-os.org/pipermail/e-lang/2010-September/013620.html Split Scope] into Scope (internal data structure for the E interpreter, including local variables, etc) and EEnv (simpler structure exposed to E code, replacing safeScope, etc). This avoids the need to tame access to these objects and hopefully makes the code easier to read.
-	* Split Scope into Scope (internal data structure for the E interpreter, including local variables, etc) and EEnv (simpler structure exposed to E code, replacing safeScope, etc). This avoids the need to tame access to these objects and hopefully makes the code easier to read.	+	* Various possible optimisations are on the '''compiler''' branch (these mostly have only a small benefit or don't work fully; otherwise I push them to next). These optimisations work for both the current E interpreter and for a possible future E compiler. There is also a very old wip-compiler branch that actually does compile E to JVM bytecode. However, it turned out that the major performance problems were elsewhere.

ThomasLeonard at 11:53, 9 November 2010

2010-11-09T11:53:12Z

←Older revision		Revision as of 11:53, 9 November 2010
Line 2:		Line 2:

	* At [http://www.it-innovation.soton.ac.uk/ IT Innovation], for some of our experimental work on service oriented architectures.		* At [http://www.it-innovation.soton.ac.uk/ IT Innovation], for some of our experimental work on service oriented architectures.
-	* At [http://0install.net/ebox.html 0install.net], as a demonstrator showing how to use 0install to run sandboxed applications with distributed ~~dependencies.~~	+	* At [http://0install.net/ebox.html 0install.net], as a demonstrator showing how to use 0install to run sandboxed applications with distributed dependency handling.
-		+
-	~~I've also made [[SAM]] - a tool for modelling the way capabilities can propagate in capability systems~~.	+

	== Branches ==		== Branches ==
Line 12:		Line 10:
	Other patches/branches:		Other patches/branches:

-	* ~~[http://www.eros-os.org/pipermail/e-lang/2010-October/013648.html~~ Make CapTP shutdown when its vat is shutdown] (on next).	+	* Make CapTP shutdown when its vat is shutdown (on next)
-	* ~~[http://www.eros-os.org/pipermail/e-lang/2010-September/013620.html~~ Split Scope] into Scope (internal data structure for the E interpreter, including local variables, etc) and EEnv (simpler structure exposed to E code, replacing safeScope, etc). This avoids the need to tame access to these objects and hopefully makes the code easier to read.	+	* Various possible optimisations are on the '''compiler''' branch (these mostly have only a small benefit or don't work fully; otherwise I push them to next)
-	* Various possible optimisations are on the '''compiler''' branch (these mostly have only a small benefit or don't work fully; otherwise I push them to next). These optimisations work for both the current E interpreter and for a possible future E compiler. There is also a very old wip-compiler branch that actually does compile E to JVM bytecode. However, it turned out that the major performance problems were elsewhere.	+	* Split Scope into Scope (internal data structure for the E interpreter, including local variables, etc) and EEnv (simpler structure exposed to E code, replacing safeScope, etc). This avoids the need to tame access to these objects and hopefully makes the code easier to read.