Re: [pypy-dev] cppyy: C++ bindings for PyPy
Hi Maciej, On Mon, 23 Apr 2012, Maciej Fijalkowski wrote:
Quick question - if it's mature, why not merge it to default? I presume it should be turned off, since there is a sizeable dependency, but still having it in default can be good.
I have a standalone version of Reflex now and made a few minor mods to cppyy to use it. That basically reduces the dependencies to Reflex (at runtime) and gccxml (for generation of reflection info, but not needed for the build or runtime). I'll update the documentation in a bit. What I'd like to have, is to defer the linking with libReflex until cppyy is imported into pypy-c. I've been unable to get that to work, though. :/ Best regards, Wim -- WLavrijsen@lbl.gov -- +1 (510) 486 6411 -- www.lavrijsen.net
Hi Wim, On Fri, May 4, 2012 at 8:16 AM, <wlavrijsen@lbl.gov> wrote:
Quick question - if it's mature, why not merge it to default? I presume it should be turned off, since there is a sizeable dependency, but still having it in default can be good.
I have a standalone version of Reflex now and made a few minor mods to cppyy to use it. (...)
I think that Fijal's suggestion was to merge the branch anyway, but keep cppyy turned off by default. I would also welcome this, but it's up to you if you prefer to keep it in a separate branch. I can give a try to lazy linking, but I fear that it's going to be OS-specific code... A bientôt, Armin.
Hi Armin,
I think that Fijal's suggestion was to merge the branch anyway, but keep cppyy turned off by default. I would also welcome this, but it's up to you if you prefer to keep it in a separate branch.
I feel better about merging now that I've created a standalone version of Reflex. However, I'll be mostly offline for the next two weeks or so, so I'll wait until after that, to be able to deal with possible fall-out. :}
I can give a try to lazy linking, but I fear that it's going to be OS-specific code...
That's in any case a separate can of worms, as nothing has yet been tested on Windows (the only Windows box that I have, has only 2GB of memory, so too little to translate, although I could try to run the tests). Best regards, Wim -- WLavrijsen@lbl.gov -- +1 (510) 486 6411 -- www.lavrijsen.net
On Wed, May 9, 2012 at 10:16 AM, <wlavrijsen@lbl.gov> wrote:
Hi Armin,
I think that Fijal's suggestion was to merge the branch anyway, but
keep cppyy turned off by default. I would also welcome this, but it's up to you if you prefer to keep it in a separate branch.
I feel better about merging now that I've created a standalone version of Reflex. However, I'll be mostly offline for the next two weeks or so, so I'll wait until after that, to be able to deal with possible fall-out. :}
There is absolutely no rush, however great news! Can you think about a blogpost describing what you did and how to use it accompanying the merge? Copy-pasting docs is fine :) Cheers, fijal
Hi Maciej,
Can you think about a blogpost describing what you did and how to use it accompanying the merge?
yes, that was the intention: I had actually already started drafting a blog post, but got distracted. For the how-to, I'd link directly to the docs: http://doc.pypy.org/en/latest/cppyy.html as there's more room there for detailed instructions. In the posting, I'd rather focus on explaining the decisions that went into the development. Cheers, Wim -- WLavrijsen@lbl.gov -- +1 (510) 486 6411 -- www.lavrijsen.net
participants (3)
-
Armin Rigo -
Maciej Fijalkowski -
wlavrijsen＠lbl.gov