[pypy-dev] SOLVED Re: Unknown Operation Re: What Causes An Ambiguous low-level helper specialization Error?

[Andrew Francis]

Hi Folks:

Silly error. I didn't notice that targetdemo.py was updated: the API changed! Using the latest version as an example, I got my example to work. Yeah!


Thanks to everyone for the help!

Cheers,
Andrew




________________________________
 From: Armin Rigo <arigo at tunes.org>
To: Andrew Francis <andrewfr_ice at yahoo.com> 
Cc: Amaury Forgeot d'Arc <amauryfa at gmail.com>; "pypy-dev at codespeak.net" <pypy-dev at codespeak.net> 
Sent: Wednesday, January 25, 2012 2:06 PM
Subject: Re: Unknown Operation Re: [pypy-dev] What Causes An Ambiguous low-level helper specialization Error?
 
Hi Andrew,

On Wed, Jan 25, 2012 at 19:56, Andrew Francis <andrewfr_ice at yahoo.com> wrote:
> I can't wait to see this code compile! Bank accounts are the "hello world"
> of transactional programming!

In case you want to avoid having to hack at RPython: by now, you can
also compile the full PyPy with transactions enabled.  You just get a
PyPy with no GC at all (so it cannot run for more than a few seconds
before running out of memory).  You then get a sane interface from the
built-in module 'transaction', and don't have to write any RPython
code.

I use the following command line (it's very fast and doesn't require
too much RAM, because of no GC):

./translate.py -O1 --gc=none --stm targetpypystandalone.py
--no-allworkingmodules --withmod-transaction


A bientôt,

Armin.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pypy-dev/attachments/20120125/c6f37227/attachment-0001.html>