Re: [pypy-dev] cppyy and callbacks
@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, <pypy-dev-request@python.org> wrote:
Send pypy-dev mailing list submissions to pypy-dev@python.org
To subscribe or unsubscribe via the World Wide Web, visit https://mail.python.org/mailman/listinfo/pypy-dev or, via email, send a message with subject or body 'help' to pypy-dev-request@python.org
You can reach the person managing the list at pypy-dev-owner@python.org
When replying, please edit your Subject line so it is more specific than "Re: Contents of pypy-dev digest..."
Today's Topics:
1. Re: cppyy and callbacks (Maciej Fijalkowski)
----------------------------------------------------------------------
Message: 1 Date: Fri, 10 Jan 2014 09:13:05 +0200 From: Maciej Fijalkowski <fijall@gmail.com> To: Alex Stewart <foogod@gmail.com> Cc: PyPy Developer Mailing List <pypy-dev@python.org> Subject: Re: [pypy-dev] cppyy and callbacks Message-ID: < CAK5idxQMp+phKVsazry6WqeqnoGSWPx5gaGL9wWrPz6fewTGBA@mail.gmail.com> Content-Type: text/plain; charset=UTF-8
On Fri, Jan 10, 2014 at 1:58 AM, Alex Stewart <foogod@gmail.com> wrote:
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. Is it actually suitable for general-purpose use?
If so, I'd certainly be happy to try it.. how would one go about switching to using the CINT backend instead of Reflex?
--Alex
Hey Alex.
On a sidenote - can you please subscribe to pypy-dev so I don't have to authorize every single one of your mail? It's relatively painless and it's also very low traffic, so you won't get much uninteresting stuff. Obviously feel free to unsubscribe once you're done.
Cheers, fijal
------------------------------
Subject: Digest Footer
_______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
------------------------------
End of pypy-dev Digest, Vol 33, Issue 6 ***************************************
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/reflex-support As for the CPython side of things, our development is in this repository: http://root.cern.ch/gitweb?p=root.git;a=summary http://root.cern.ch/git/root.git the bindings are under bindings/pyroot. You'll find that they're too entangled to use (other than by building/installing the whole project, which could be an option as it's not _that_ bad). More direct access to cling (we've tried to prevent LLVM headers from leaking into user code, so everything is hidden under at least one layer) can all be found in core/meta. For bug reports etc., here's the project JIRA: https://sft.its.cern.ch/jira/browse/ROOT https://sft.its.cern.ch/jira/browse/ROOT/component/10760 Best regards, Wim -- WLavrijsen@lbl.gov -- +1 (510) 486 6411 -- www.lavrijsen.net
participants (2)
-
Dimitri Vorona -
wlavrijsen＠lbl.gov