Mailing lists

Christophe Haro asked me a very interesting question today: how does one contact the LibertyEiffel community?

There was no mailing list ten minutes ago. Now there is.

Just write to libertyeiffel@librelist.com and you're done!

See their site (http://librelist.com) for details. In a nutshell, when you send your first mail you are returned a standard subscription mail; just answer it and you're set.

Welcome on board!

Getting organized.

Thanks to the new github "organization", LibertyEiffel has now gained a central depot independantly to the developers.

You can find the code there: http://github.com/LibertyEiffel/Liberty

Tickets should be opened there too.

How easy should it be to install Liberty?

That easy:

$ ./install.sh

And now it is that easy.

The toddler starts to run

Starting with commit e5799, the interpreter correctly runs arithmetic tests. It is more important than it seems: it means that arithmetic types are correctly promoted (think conversion + a specific conversion of Current for symmetry).

I think I'll start working on agents now, otherwise a lot of tests won't run (see EIFFELTEST_TOOLS which is agent-based)

Hello, World!

To the immense joy of its parents, the Liberty Interpreter is born today: the classic Hello World program runs successfully.

Liberty is still a toddler: a lot or things are yet to be fixed or even merely implemented (semantic checks, agents, garbage collection, to cite just a few).

Its younger brother, the Liberty Compiler, is still a frozen embryo :-)

Anchors may drag you down.

Anchors are a Real Good Thing (TM). But the compiler is pretty involved in their evaluation.

Liberty will use the same strategy as SmartEiffel: feature specialization. Each type specializes its features to eliminate anchors while correctly resolving them.

This creates a full flotilla of features... but their buoyancy is improved.

The Liberty Interpreter

The interpreter starts to work!

Objects are correctly created, features are called, contracts are checked, built-ins will be finished in a matter of days...

Now I need ideas for an efficient plugins implementation.

Although I have a few ideas (far from being ripe!) I'd be glad if some people could propose something.

What do you have in mind? Just go wild :-)