[pypy-dev] pypy-dev Digest, Vol 310, Issue 5

Grégoire Dooms dooms at info.ucl.ac.be
Wed May 24 09:06:20 CEST 2006

> Date: Fri, 12 May 2006 12:42:17 +0200
> From: Aur?lien Camp?as <aurelien.campeas at logilab.fr>
> Subject: Re: [pypy-dev] Thread cloning (coroutine cloning, really)
> To: Armin Rigo <arigo at tunes.org>
> Cc: pypy-dev at codespeak.net
> Message-ID: <20060512104217.GB28391 at crater.logilab.fr>
> Content-Type: text/plain; charset=iso-8859-1
> We could restrict the programming style for code to be running inside
> comp. spaces but if it is possible to effectively clone everything
> (for some ill-defined notion of everything) then it'l be fine. I'm not
> 100% sure. Here are some of the constraints :
> In principle, side-effects on the parent space and the outer world
> should be forbidden from within a running comp. space ('cause the jury
> is still out on its outcome).

If I can throw in my two cents, you should really try to remove this 
limitation of Mozart. This is a real pain in the ass when you want to 
know what happens in a space (I used to need that in Mozart for 
debugging or statistics). In Mozart it is possible to use a hack in 
order to have side effects out of a space (ie modifiy state outside the 
space)  by using ports.
I think a design which would allow it would be much more Pythonic (we 
are between consenting adults :-)


More information about the Pypy-dev mailing list