On 18 April 2013 20:35, stephane ducasse <stephane.ducasse@free.fr> wrote:
On Apr 18, 2013, at 8:19 PM, Igor Stasenko <siguctua@gmail.com> wrote:
On 18 April 2013 19:17, Nicolas Cellier <nicolas.cellier.aka.nice@gmail.com> wrote:
Sure, typical refactoring process. Code is convoluted and hard to follow, so you first document and explicit most obscure steps. In a second time, you realize how simpler it could be...
Pharo is quite fast and still accelerating these days, so I understand the "satisfecit", it's already huge progress. My unsatisfied nature just tell to not stop in the middle of the bridge, and to not let un-necessarily complex code, even if well commented :)
Opal is there we all can start contributing. I, for instance, have plans for replacing parsing.. to make modular parser & encoder
Yes :) I would like to have a compilationContext instead of this ugly full of parameter methods and â¦.
I would like to be able to specify an environment (class binding + literal binding) as input and an environment as output so that we can bootstrap the compiler nicely and do a lot fun stuff.
Take a look at Colin Putney's Environments stuff. Seriously. It's all there. Compilation contexts, class bindings, various policies for importing/exporting definitions. It just needs forging in the hands of users. frank
Stef