I don't remember why I put that dependency on the startup list for OSProcess, but I'll take a look at it this weekend and see if there is a better way. Probably it was just to ensure that file related things were initialized prior to starting OSProcess initialization.
Dave On Fri, May 20, 2011 at 08:26:59PM +0200, St?phane Ducasse wrote: > Adrien > > people do not realize that you are not maintaining OSProcess :) > So we should check and publish a new version of OSProcess with a difference > startUpDependency. > > On May 20, 2011, at 5:07 PM, Adrien BARREAU wrote: > > > Hi all, > > > > I just tried to load OSProcess in the last PharoCore 1.3 (I took it from > > hudson). It fails when it tries to add ThisOSProcess to the startup list > > with: > > Smalltalk addToStartUpList: ThisOSProcess after: ImageSegment. > > in ThisOSProcess class>>initialize. > > > > > > It seems that ImageSegment is not in the StartUpList anymore. > > Is that normal? > > > > Adrien. >
