https://github.com/opencv/opencv/issues/6585#issuecomment-221842441 snip:
> "C-API" is not supported and should be removed totally (but we have a lack of > resources to port this legacy C code to C++, so some of this code still > exists right now). Also huge part of fresh OpenCV functionality is missing in > "C-API". There is no plan to fix this in OpenCV directly. http://answers.opencv.org/question/17546/opencv-will-drop-c-api-support-soon/ snip: > Shervin is right, the C API is not developed for a long time. All the new > stuff has the C++ API, and it is not backported to the C. So, C API becomes > obsolete and causes pain in the neck, since it should be maintained I recommend trying out Calypso and helping ironing out any bugs you may find. On Mon, Feb 5, 2018 at 3:15 AM, Kagamin via Digitalmars-d-learn <digitalmars-d-learn@puremagic.com> wrote: > On Sunday, 4 February 2018 at 08:33:20 UTC, Mike Parker wrote: >> >> Though, I'm curious why anyone would want to declare a callback in a C++ >> program as cdecl only on Windows and use the default C++ convention >> everywhere else. I suggest you dig into it and make sure that's what's >> intended. And good luck binding to OpenCV! >> >> >> [1] >> https://github.com/opencv/opencv/blob/master/modules/core/include/opencv2/core/types_c.h#L68 > > > No, it's C everywhere, see > https://github.com/opencv/opencv/blob/master/modules/core/include/opencv2/core/types_c.h#L1774
