We provide a variety of factory functions for transforming proxies, proxies which themselves are split into 2 parts:
A user-facing interface (like GreeterPrx)
An 'internal' class which implements the interface (like GreeterPrxI)
All the logic for these factory functions is on the interface, instead of the class.
Which is kind of weird on it's own: usually implementation is done by classes, not interfaces.
But our setup is worse because the interface implementations all look like:
Since they're interface methods, they're completely public, which is kind of lame.
This PR removes all the implementation logic from the interface side.
Now the interface just has: ObjectPrx ice_adapterId(...); a 'pure virtual function'.
And these implementations were moved into the corresponding class.
This completely eliminates these unfortunate hidden-underscore-methods.
We provide a variety of factory functions for transforming proxies, proxies which themselves are split into 2 parts:
GreeterPrx)GreeterPrxI)All the logic for these factory functions is on the interface, instead of the class. Which is kind of weird on it's own: usually implementation is done by classes, not interfaces. But our setup is worse because the interface implementations all look like:
Since they're interface methods, they're completely public, which is kind of lame.
This PR removes all the implementation logic from the interface side. Now the interface just has:
ObjectPrx ice_adapterId(...);a 'pure virtual function'.And these implementations were moved into the corresponding class. This completely eliminates these unfortunate hidden-underscore-methods.