Ecru 0.1.3

Code reorganization and improvements to the Python interface, along with the beginnings of concurrency support. Script for running the REPL is now named 'ecru'.

Milestone information

Project:
Ecru
Series:
trunk
Version:
0.1.3
Released:
2008-08-30  
Registrant:
Allen Short
Release registered:
2008-08-30
Active:
No. Drivers cannot target bugs and blueprints to this milestone.  

Download RDF metadata

Activities

Assigned to you:
No blueprints or bugs assigned to you.
Assignees:
No users assigned to blueprints and bugs.
Blueprints:
No blueprints are targeted to this milestone.
Bugs:
No bugs are targeted to this milestone.

Download files for this release

After you've downloaded a file, you can verify its authenticity using its MD5 sum or signature. (How do I verify a download?)

File Description Downloads
download icon ecru-0.1.3.tar.gz (md5, sig) Ecru 0.1.3 7
last downloaded 100 weeks ago
Total downloads: 7

Release notes 

Basic support for vats has been added, and the Python interface is now entirely implemented in a C extension module instead of using ctypes. Scripts now can be queried for approval stamps, and the 'Selfless' stamp has been added for use by the equalizer. Map objects, for example, now compare properly for equality.

Changelog 

View the full changelog

 - Renamed the repl script to 'ecru' for consistency.
 - Converted global exception/ejection state into thread-local state.
 - Objects can now be given approval stamps by stamping auditors.
 - Initial implementation of the 'Selfless' stamp and its use in the equalizer
   for object comparison, along with '__optUncall' methods for some objects.
 - Initial implementation of vats. Messages can can be queued and executed
   within a vat from C.
 - Reimplementation of the Python bridge entirely in C, using the vat interface
   for code execution.
 - Integration tests converted to Python unit tests.
 - Reorganization of objects implemented in C into separate source files.
 - Inclusion of build-aux files.

0 blueprints and 0 bugs targeted

There are no feature specifications or bug tasks targeted to this milestone. The project's maintainer, driver, or bug supervisor can target specifications and bug tasks to this milestone to track the things that are expected to be completed for the release.

This milestone contains Public information
Everyone can see this information.