Oh well, sorry. I checked and ... it seemed taskit could do it, but now it seems to be a future extension. However OSProcess can do it: look at #forkSqueak.
Thierry Le mer. 9 janv. 2019 à 21:36, Thierry Goubier <thierry.goub...@gmail.com> a écrit : > > Hi Alexandre, > > look at taskit: (https://github.com/sbragagnolo/taskit). I think it > can do what you are looking for. I think that OSProcess is also able > to do that via fork calls. > > Having minimal, light weight images without complex loading > preferences and whatever would help, otherwise simply forking your > current image could be faster. > > Thierry > > Le mer. 9 janv. 2019 à 19:42, Alexandre Bergel via Pharo-users > <pharo-users@lists.pharo.org> a écrit : > > > > Hi! > > > > Is there an effort to easily use multi-core or native processes in Pharo? > > I am thinking about a library that offer a construct like: > > > > future := Runner runInDifferentProcess: [ “This block is run in a different > > OS process” ] > > > > That would save the image under a different name, use OSSubProcess to > > launch a new Pharo with no UI. > > > > Is there a library available? > > > > Cheers, > > Alexandre > > -- > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > Alexandre Bergel http://www.bergel.eu > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > >
