search for: cppyy

...ve a patch yet but has an open projects entry and somebody working on it). These patches can be considered in parallel independently on the rest. Extend and Generalize the Language Interoperability Layer Around Cling --- HEP has extensive experience with on-demand python interoperability using cppyy[6], which is built around the type information provided by cling. Unlike tools with custom parsers such as swig and sip and tools built on top of C-APIs such as boost.python and pybind11, cling can provide information about memory management patterns (eg refcounting) and instantiate templates o...

...try and somebody working on it). These patches can be considered in parallel independently on the rest. >> >> Extend and Generalize the Language Interoperability Layer Around Cling >> --- >> >> HEP has extensive experience with on-demand python interoperability using cppyy[6], which is built around the type information provided by cling. Unlike tools with custom parsers such as swig and sip and tools built on top of C-APIs such as boost.python and pybind11, cling can provide information about memory management patterns (eg refcounting) and instantiate templates on th...

...nsidered in parallel independently on the rest. >>>> >>>> Extend and Generalize the Language Interoperability Layer Around Cling >>>> --- >>>> >>>> HEP has extensive experience with on-demand python interoperability >>>> using cppyy[6], which is built around the type information provided >>>> by cling. Unlike tools with custom parsers such as swig and sip and >>>> tools built on top of C-APIs such as boost.python and pybind11, >>>> cling can provide information about memory management pat...

...king on it). These patches can be considered in parallel independently on the rest. >>> >>> Extend and Generalize the Language Interoperability Layer Around Cling >>> --- >>> >>> HEP has extensive experience with on-demand python interoperability using cppyy[6], which is built around the type information provided by cling. Unlike tools with custom parsers such as swig and sip and tools built on top of C-APIs such as boost.python and pybind11, cling can provide information about memory management patterns (eg refcounting) and instantiate templates on th...

...somebody working on it). These patches can be > considered in parallel independently on the rest. > > Extend and Generalize the Language Interoperability Layer Around Cling > --- > > HEP has extensive experience with on-demand python interoperability > using cppyy[6], which is built around the type information > provided by > cling. Unlike tools with custom parsers such as swig and sip and > tools > built on top of C-APIs such as boost.python and pybind11, cling can > provide information about memory management patterns (eg...

Last time this came up, there were a lot of people that were stuck on GCC 4.9 due to ABI reasons. I think forcing that upgrade is going to be the most disruptive part of this, and I think that will really need a decent amount of time. =[ On Thu, May 10, 2018 at 2:26 PM JF Bastien via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > On May 10, 2018, at 12:25 PM, Evgeny Astigeevich