Re: [pypy-dev] cppyy and callbacks

2014-01-10 Thread Alex Stewart
Hey Wim, Thanks for all the useful info on the status of things! > Overriding of virtual functions can only be done with a helper class > deriving from the callback interface on the C++ side. There's no other > (portable) way. Yeah, I kinda figured this would be required regardless, and that b

Re: [pypy-dev] cppyy and callbacks

2014-01-10 Thread Alex Stewart
> > On a sidenote - can you please subscribe to pypy-dev so I don't have > to authorize every single one of your mail? I'm a bit confused.. I've been subscribed to pypy-dev (and receiving list mail) since some time in August. (I just went to the mailman page for the list and logged in with my pa

Re: [pypy-dev] cppyy and callbacks

2014-01-10 Thread wlavrijsen
Hi Alex, I'd looked around a bit but could only find vague references to CINT, and it wasn't even clear to me whether a full CINT backend really existed or it was just a hack/experiment. it's quite alive; in high energy physics, Reflex is only used by mapping Reflex information into CINT, then

Re: [pypy-dev] cppyy and callbacks

2014-01-10 Thread wlavrijsen
Hi Dimitri, Where could I find the current state of the cling backend implementation? remember, I only just started (as in: a couple of days ago); the code does not currently compile, let alone run a single test. When it gets there, it'll appear here: https://bitbucket.org/pypy/pypy/branch/

Re: [pypy-dev] pypy-dev Digest, Vol 33, Issue 6

2014-01-10 Thread Dimitri Vorona
@Wim Where could I find the current state of the cling backend implementation? Regards, Dimitri. On Fri, Jan 10, 2014 at 12:00 PM, wrote: > Send pypy-dev mailing list submissions to > pypy-dev@python.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://ma

Re: [pypy-dev] cppyy and callbacks

2014-01-10 Thread Dimitri Vorona
@Wim Where could I find the current state of the cling backend implementation? Regards, Dimitri. PS. Please, ignore the email with the wrong subject. > On Fri, Jan 10, 2014 at 12:00 PM, wrote: > >> Send pypy-dev mailing list submissions to >> pypy-dev@python.org >> >> To subscribe or u

Re: [pypy-dev] ctypes create_string_buffer

2014-01-10 Thread Armin Rigo
Hi, On Fri, Jan 10, 2014 at 2:52 PM, Kenny Lasse Hoff Levinsen wrote: > On 09/01/2014, at 14.30, HY wrote: > import ctypes as C > s1= "0"* 1024* 1024* 10 > # mem engross add 10M bytes > b1= C.create_string_buffer(s1 ) > # CPU 1 core 100% and mem engross add 300M bytes ? > I don't know! > please

Re: [pypy-dev] ctypes create_string_buffer

2014-01-10 Thread Kenny Lasse Hoff Levinsen
ctypes is not nice to use. If you need C-bindings, please look at CFFI. Sent from my iPhone > On 09/01/2014, at 14.30, HY wrote: > > import ctypes as C > s1= "0"* 1024* 1024* 10 > # mem engross add 10M bytes > b1= C.create_string_buffer(s1 ) > # CPU 1 core 100% and mem engross add 300M bytes

Re: [pypy-dev] Boost.Python and PyPy -- status?

2014-01-10 Thread Toby St Clere Smithe
Hi Amaury, Thanks for responding. "Amaury Forgeot d'Arc" writes: > I just did it again, with Boost 1.55: > > - Apply the patch in > > https://bitbucket.org/pypy/pypy/src/default/pypy/module/cpyext/patches/boost.patch > > - EXCEPT the "using python" part, which should be something like: > > using