Python is in the same situation, what Python coders do is span processes, in this case OS process which is an instance of python interpreter , the advantage of an OSprocess is that it can run on a separate core in case you have a multicore cpu. This way you get true concurrency. However OS process are isolated so you will have to make them communicate via sockets or pipes. Python has such libraries to facilitate easy communication between processes.
In case of Pharo you would be opening Pharo headless several times, one instance for each concurrent task you want. This way you will get non blocking code and able to take advantage of all the cores of your cpu. On Thu, Nov 21, 2013 at 1:38 PM, Marcus Denker <[email protected]>wrote: > > On 21 Nov 2013, at 12:33, Yuriy Tymchuk <[email protected]> wrote: > > > On 20 Nov 2013, at 20:58, Clément Bera <[email protected]> wrote: > > So what you are looking for is Process and semaphores. > > This is not multithreading in the default Pharo VM + image, currently our > semaphore/process management is not multithreaded, but executes all the > process in the same thread. > > > Ouch. Do you know if this is planned for any milestone? > > > It is a problem that is far from simple to solve. Just defining a > milestone will not help anything. > > Marcus >
