There is eoc, a command line tool that helps you automate compilation, transpilation, and execution of simple EO programs. With this tool you can also create and execute unit tests. Just name them *-test.eo and add metas +junit to them.

Since version 0.23.8 it is possible to use string.slice object just like this:

"Привет".slice 1 2

Here, the slice object returns the “ри” string, which is a substring of the “Привет” string from the specified start position and with the length len.

If the above parameters are out of bounds, slice will return an error object instead of a new string object.

Until version 0.23.7 it was possible to use memory object just like this:

memory > m
m.write 42

On the first line, a copy of memory was made and then labeled as m. This was a bug in the language. The object memory must not be copied if there are no arguments provided for the copying (application) operation.

Since version 0.23.6 of EO we got rid of the char object. We want to simplify the core of the language and believe that this object can be easily replaced with its actual representation, i.e. an array of bytes. Now, if you want to get a character, you can just use the string object instead. All of these examples are valid strings: "\u0123", "h", "\t", "\n" and "\07". We got rid of the string.char-at and bytes.as-char objects.

EO is a new experimental programming language. EO is not planning to become a mainstream language—this is not what we want. Our main goal is to prove to ourselves that true object-oriented programming is practically possible. Not just in books and abstract examples, but in real code that works. That’s why EO is being created—to put all those “crazy” pure object-oriented ideas into practice and see whether they can work.