Re: [Pharo-dev] DelayScheduler cleanup & Bootstrap

2018-04-20 Thread Stephane Ducasse
> > I had hoped it would be something simple like that. >>> Thanks for confirming. >>> >>> This is power of having a working bootstrap! Thanks Ben for helping improving Pharo.

Re: [Pharo-dev] DelayScheduler cleanup & Bootstrap

2018-04-19 Thread Ben Coman
On 19 April 2018 at 15:38, Guillermo Polito wrote: > > > On Sun, Apr 15, 2018 at 3:19 PM, Ben Coman wrote: > >> I am doing a pass to cleanup the DelayScheduler hierarchy. >> I'll be refactoring of the hierarchy to aid code understanding >> and

Re: [Pharo-dev] DelayScheduler cleanup & Bootstrap

2018-04-19 Thread Guillermo Polito
On Sun, Apr 15, 2018 at 3:19 PM, Ben Coman wrote: > I am doing a pass to cleanup the DelayScheduler hierarchy. > I'll be refactoring of the hierarchy to aid code understanding > and eliminate redundant instance variables from the original code. > The target structure is

Re: [Pharo-dev] DelayScheduler cleanup & Bootstrap

2018-04-18 Thread Stephane Ducasse
Thanks Ben this is great to see this happening. Thanks again. Now about your question: I do not know and we should document it better, but everything in the in github bootstrap + the scripts Guillermo is teaching somewhere in France coming friday like me. On Sun, Apr 15, 2018 at 3:19 PM, Ben

[Pharo-dev] DelayScheduler cleanup & Bootstrap

2018-04-15 Thread Ben Coman
I am doing a pass to cleanup the DelayScheduler hierarchy. I'll be refactoring of the hierarchy to aid code understanding and eliminate redundant instance variables from the original code. The target structure is DelayNullScheduler -- minimum interface to avoid errors in rest of system (6