I’m looking at the API for Ocaml, which has a strongly typed OOP, and there’s a kind of chicken/egg problem with the two OOP systems put together - the C++ object needs the Ocaml callbacks for the hook virtual functions that the class will provide, and the class needs the object in order to be constructed. I might be able to figure out some other way around this if necessary, but at the moment I seem to be able to make it work by simply doing the `derived class’ initialization, from Ocaml, after the object has returned from the constructor.
So B_my_wrapper_Window(…): BWindow(…) { } // i.e., the C++ classes never do anything beyond their constructors from the factory, and custom view children etc. all are added at a later time. Well, immediately later.
Am I missing some common case where derived classes need to work something out before the constructor returns? So far I’ve only OOP-ified BWindow.
With the non-OOP side of Ocaml I can call back to an initialization function - that works OK.
. Maybe it would help if you wrote a more in-depth explanation of what you’re trying to do. I have experience with writing Python API bindings, so, I might know the solution to the chicken and egg problem that you’re encountering, but I’m not exactly sure what the chicken and egg problem is.