1 | initial version |
there already exist a couple of similar issues -- in the end it's a "won't fix".
if you want my 2ct. here: avoid clr / managed code. opencv uses a RAII based programming model, 4.0 will heavily use c++11 features, all of it incompatible to managed c++. (the mutex problem is only the tip of the iceberg)
2 | No.2 Revision |
there already exist a couple of similar issues
though there are attempts to mend it -- in the end it's a "won't fix".
if you want my 2ct. here: avoid clr / managed code. opencv uses a RAII based programming model, 4.0 will heavily use c++11 features, all of it incompatible to managed c++. (the mutex problem is only the tip of the iceberg)
3 | No.3 Revision |
there already exist a couple of similar issues
though there are attempts to mend it -- in the end it's a "won't fix".
if you want my 2ct. here: avoid clr / managed code. opencv uses a RAII based programming model, 4.0 will heavily use c++11 features, all of it incompatible to managed c++. (the mutex problem is only the tip of the iceberg)iceberg, you can't have a cv::Mat or a Ptr as a classmember, but need pointers to those (defeating the purpose of refcounting))