> On 12 ene 2016, at 8:53 p.m., stepharo <[email protected]> wrote: > > > +1111^1111111 >> >> We should make a list. Some that should be easy: >> >> - Delay should be splitted > why?
First, I mean Delay, not processes. Processes are required for executing code, delays are not. I believe that Delay is not a language kernel concern. It is an important concern but not a Kernel one. Also, - the biggest it is the Kernel package, the more difficult it is to analyze dependencies (because everything depends on kernel so who would care, no?) - I could imagine little images that do not contain delay, because they do not use it. Of course, it is not the typical Pharo distribution but it is a possible case. I only say that having it in a separate package is worth it. Check senders of wait, you will see that the usages inside the kernel are really few: mainly BlockClosures implementing things like #valueAndWait and Delay tests. > >> - Chronology should be splitted >> >> One more complicated: >> >> - InstructionClient and InstructionStream should be splitted >> >> And then, we should also review the API of basic objects >> >> Object methods size => 385 >> Integer methods size => 182 >> ... > >
