Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Why opencv changed its API for feature detection in 3.0.0

I understand that this is more of a rant than question but is also being posted out of curiosity. Why on earth did opencv change APIs for a perfectly stable module (features2d and nonfree (sift and surf) ). Are they really that jobless or is there a specific reason for this ?

It's broken quite a bit of my code and now I have spent about 5 hours fixing it and will be here all night. Thanks for that !!

Why opencv changed its API for feature detection in 3.0.0

I understand that this is more of a rant than question but is also being posted out of curiosity. Why on earth did opencv change APIs for a perfectly stable module (features2d and nonfree (sift and surf) ). Are they really that jobless or is there a specific reason for this ?

Also, cv::Ptr changed too ! I can understand this might introduce safety but should constructors not have been explicit in the first design itself !

It's broken quite a bit of my code and now I have spent about 5 hours fixing it and will be here all night. Thanks for that !!