missing const or CV_IN_OUT keyword in method signatures (Bugfix #3111)


Added by Alexander Duda over 11 years ago. Updated over 11 years ago.


Status:Open Start date:2013-06-22
Priority:Normal Due date:
Assignee:Vadim Pisarevsky % Done:

0%

Category:python bindings
Target version:-
Affected version:branch 'master' (2.4.9) Operating System:Linux
Difficulty:Easy HW Platform:x64
Pull request:

Description

The follwing methods have a discrepancy between their signature and their binding description. Ideally the const keyword should be added but I am not sure if this is allowed because it would alter the interface.

This code is used to patch the output of hdr_parser.py before ffi ruby bindings are generated from it:

BRISK.generateKernel.parameter(0).add_flag(:IO)
BRISK.generateKernel.parameter(1).add_flag(:IO)
BRISK.operation("BRISK")[1].parameter(0).add_flag(:IO)
BRISK.operation("BRISK")[1].parameter(1).add_flag(:IO)

randShuffle.parameter(2).add_flag(:IO)
putText.parameter(0).add_flag(:IO)
chamerMatching.parameter(0).add_flag(:IO)
chamerMatching.parameter(1).add_flag(:IO)
chamerMatching.parameter(2).add_flag(:IO)


Associated revisions

Revision 90905fb1
Added by Vadim Pisarevsky over 10 years ago

Merge pull request #3111 from vpisarev:make_ximgproc_compile

History

Updated by Kirill Kornyakov over 11 years ago

Andrey, could you please check this?

Alexander, am I right that somebody is working on Ruby bindings for OpenCV? Could you please share more information about this??

  • Description changed from The follwing methods have a discrepancy between their signature and their bin... to The follwing methods have a discrepancy between their signature and their bin... More
  • Tracker changed from Bug to Bugfix
  • Status changed from New to Open

Also available in: Atom PDF