On Sun, Dec 1, 2013 at 11:44 AM, Clément Bera <bera.clem...@gmail.com>wrote:
> One thing with Pharo 3.0 is that the debugger is quite different than it > used to be. > > It is now split into a model (DebugSession + DebugContext) and the view, > SpecDebugger. I don't know what Eliot does have to change but the new code > may require some extra work due to the debugger being different. > The code is all down at the level of ContextPart so I hope it won't affect the debugger changes at all. > > Now the new debugger is so much easier to understand and to edit that it > shouldn't be an issue... > > > 2013/12/1 Stéphane Ducasse <stephane.duca...@inria.fr> > >> >> On Dec 1, 2013, at 6:11 PM, Esteban A. Maringolo <emaring...@gmail.com> >> wrote: >> >> > 2013/12/1 Stéphane Ducasse <stephane.duca...@inria.fr>: >> >> Hi eliot >> >> >> >> why in pharo 2.0? >> >> Do you have some specific scenario? Because it would be better to have >> it in >> >> Pharo 30 alpha. >> > >> > In ten days I'll put a system into production (cross your fingers). It >> > is built with Pharo 2 (what else?). >> >> Excellent news! >> Will you be able to tell us more because Pharo needs more visibility. >> >> > So having this... will certainly help those who, like me, don't live >> > in the bleeding edge. And will need to support (hence debug) a running >> > system. >> >> I tend not to rely on just introduced features even in 2.0 and also >> introducing something new can always >> have side effect. >> >> > >> > Regards, >> > >> > Esteban A. Maringolo >> > >> >> >> > -- best, Eliot
