no idea but I want to know that too so keep us posted. On Sep 29, 2010, at 9:59 AM, Stefan Marr wrote:
Hi:
The naive approach of subclassing Process and writing my own fork/spawn does not seem to work for some reason.
I tried:
Erlang>>spawn: aBlock "Answer an ErlProcess running the code given in the parameter. The process is scheduled." | proc | proc := ErlProcess forContext: [aBlock value. Processor terminateActive] asContext priority: Processor activePriority. proc resume. ^ proc
This is basically what happens in BlockClosure newProcess.
However, since I do not want to modify BlockClosure, it is not operating on self anymore ('self value' became 'aBlock value', which seems to pose a problem. For some reason, the created process crashes on accessing aBlock, were I would expect it to be available since the block is a closure, right? Looks to me like asContext is doing something I would have to replicate, too.
Has someone done something similar before?
Thanks Stefan
-- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project