wlav

Problem is that the older interface is still being used in PyPy. Of course, there it's the C-API, not the C++ one, so as long as the C version can...

The C-API is also in `clingwrapper.cxx`, and currently, it just forwards (after dealing with things such as `std::string` and other C++ types): https://github.com/wlav/cppyy-backend/blob/master/clingwrapper/src/clingwrapper.cxx#L2766

Again, on your side, sure. As a pull request on this repo, no, b/c PyPy. AFAICT, the C API still uses it: https://github.com/wlav/cppyy-backend/blob/master/clingwrapper/src/clingwrapper.cxx#L2766

> The problem with GetMethodSignature vs GetMethodPrototype (or whatever their exact naming is) is mostly in the show formal args parameter. For improvement, maybe start with going back to their...

Yes, on the Cling side, the redeclaration simply masks the first declaration. Ie., there are 2 global variables named `x` in the system; it's not an update of the original...

Yes. Lookups are slow b/c on the Python side, all that is known is that name `x`, not what it is and thus where to find it. I.e., there's a...

> And you can't use CPython extensions in PyPy. Yes, you can. Pythonizations and cppyy are a separate issue as I haven't kept the PyPy/cppyy implementation up to date due...

Two points: first, don't change comment indentation (I know the style is a bit unusual, but the reason for it is that it makes super-easy to read either the code...

I wouldn't uncomment the TPyClassGenerator file as it really can't compile at this point. It accesses ROOT headers directly rather than clingwrapper APIs. The point of that file was to...

Deep in Clang, that's wild. :/ Yes, I can reproduce it. The crash is in Cling calculating the offset of `v` into the struct `S` (it's `0` here). Such offsets...