Pharo minimal & bootstrapping - Time & DelayScheduler
A question on the minimization of the Pharo image and bootstrapping... Is there a desire to ultimately get down to the point of starting without the Time class and/or without the DelayScheduler class? DelayScheduler currently depends on Time, only due to calling "Time microsecondClockValue' which is <primitive: 240> so this dependency could be removed by copying #microsecondClockValue to DelayScheduler. How a bad is it to have one primitive invoked from two different methods? cheers -ben
Hi Ben Le 17/7/16 à 14:06, Ben Coman a écrit :
A question on the minimization of the Pharo image and bootstrapping... Is there a desire to ultimately get down to the point of starting without the Time class and/or without the DelayScheduler class?
Right now I do not think that we are targeting such situation.
DelayScheduler currently depends on Time, only due to calling "Time microsecondClockValue' which is <primitive: 240> so this dependency could be removed by copying #microsecondClockValue to DelayScheduler.
How a bad is it to have one primitive invoked from two different methods?
This is not that bad.
cheers -ben
participants (2)
-
Ben Coman -
stepharo