On 30 avr. 2013, at 13:19, Marcus Denker wrote:
On Apr 30, 2013, at 1:06 PM, Igor Stasenko <siguctua@gmail.com> wrote:
On 30 April 2013 07:50, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote: Hi guys
I thought that Pharo 20 got a lot of improvements but when I see Pharo 30, it feels like Pharo 30 is already a big step forward. This is really positive energy. When fernando will arrive we will move some efforts to Morphic so thanks you all for this cool feeling.
Stef
Yes, Opal opened doors for so many improvementsâ¦
We started to re-vive Reflectivity (Camille and me).
http://scg.unibe.ch/research/reflectivity
Status: Camille is implementing an AST transformer that takes an AST annotated with Meta Links to produce a new AST. Me: Refactoring like mad the 3.0 and Opal with the goal to be able to add the Transformer as a plugin to the compilation chain.
For now the AST transformer puts blocks everywhere because it's simpler. For example, if a node has the five possible links (before, instead, onSuccess, onError, after), it's expanded like this: [ <before link>. <instead link> ] onSuccess: [ <onSuccess link> ] onError: [ <onError link> ] ensure: [ <after link> ] It is far from being optimal but I think it will be fast enough for most use cases (one rarely needs more than one link per node).
Marcus.