Hi Gergo, Murray, Just writing up the GEP proposal for adding the C++ bindings into the mainline; and I must admit, the more I look at it - the less convincing the case seems to me. Any chance you guys could have a look at this ? I'm beggining to lean towards adding some interfaces that we can support to help you ... Thanks, Michael. -- mmeeks@gnu.org <><, Pseudo Engineer, itinerant idiotTitle: REQUIREMENTS GEP 1: ORBit C++ bindings
We need to integrate the C++ bindings for ORBit2, it's not clear how to do this, we also need a new maintainer for it.
Since the C++ bindings involve using a fairly large amount of ORB internal API, it is undesirable to split them from the ORB. These APIs include the binary servant layout and idl-compiler interfaces. It's possible that we could work exposing these.
Introducing the C++ bindings into core ORBit2 may cause portability problems, and while these can be obviated by a conditional build, this seems problematic.
The C++ bindings are however, immature and should not be considered ABI stable, however - since they have to conform to the standard CORBA C++ binding perhaps this is no problem.
The C++ bindings would need a separate maintainer, but it would seem to make some sense to have these modules in the same place.
So far none.