On May 20, 2013, at 7:00 AM, seaside@rmod.lille.inria.fr wrote:
Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter!
### Here's what I've been up to since the last WhatsUp:
- Opal major progress. -> 20 Issue tracker entries left -> 20 Regression tests failing (most are tests specific to old compiler)
### What's next, until 2013-05-31 (*):
Finishing touches⦠--------------------------- -> Fix all failing regression tests Opal -> Fix bug Semantic Analysis for AST Interpreter -> merge Guille's changes to use Opal Semantic Analysis in AST Interprer -> Change Gisela's AST Suggestions/Navigation to use Opal Semantic Analysis -> Remove RB-AST-Semantics Package -> Check all remaining references to Compiler (and other classes) -> Move old Compiler to OldCompiler Package and make it unloadable Plugability --------------- -> Clients should be able to replace all components (Parser, ASTTranslater, SemCheck, BytecodeBuilder, IRBuilder). This is quite easy: we change the CompilationContext to provide the default classes. Just set your own. -> Add Plugin architecture for SemanticCheck Plugins and AST Transformation Plugins. If you just want to do something in addition, no need to override visitors: there should be a way to just subclass a pre-defined abstract visitor and a way to define order and Setting supportâ¦. Reflectivity -------------- -> Iterate with Camille on the reimplementation of Reflectivity. -> Add ReflectiveMethod to Pharo3. -> First Link-Inliner as Plugin for Opal. When all this is Done: =================== -> add entry to Suggestions Menu "Halt Once Here" which will just annotate this AST node with a meta-link which deinstalls itself and calls Halt. The Reflectivity model is quite powerful, and we can then build things on top that would be even unthinkable without⦠AST Everywhere + Slots + Reflectivity⦠this will be great :-) Marcus