Productize C++ binding about corto HOT 2 CLOSED

I'm drastically increasing the scope of this ticket, from simply fixing this error to a complete revamp of the C++ binding. The reason for this is because I'd rather not spend time on fixing the C++ binding as is.

The current implementation is a prototype through which I was able to research different strategies for mapping the type system to C++. As such the current binding has some good ideas and it "proofs the concept" but it is nowhere near complete. As a result, code written with this binding too often needs to break the C++ abstraction to get something done.

The design goals for the C++ binding are to achieve:

• An as close as possible mapping from the Hyve type system to C++. Code written with the C++ language binding should look as much as possible like idiomatic C++ code.
• The API should be stateless. This means that the C++ objects refer and "wrap" hyve objects. They don't copy values between C and C++. Translation to C++ "native" types will be done by accessor methods. This by the way poses an interesting design challenge for collections.
• The C++ binding should be generated from the type system wherever possible. Metaprocedures in particular could potentially enable a language binding that is fully generated using hyve C++ code generators. This would be incredibly advantageous since the only thing that would need to be maintained would be the code generators. The current prototype generates most of the code, though some of it is manual.

from corto.

Issues of C++ binding will be captured on cortoproject/cpp repository.

from corto.