Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Set of fixes for function signatures in derived classes that may (potentially) lead to logic bugs #35

Merged
merged 5 commits into from
Sep 16, 2018

Conversation

karpov-sv
Copy link
Contributor

Several of derived classes have methods with signatures different from base virtual ones, for no obvious reason. Seems they will not be called as a result, that may lead to logic bugs somewhere.
Petr, please check whether these changes were intended, or just a mistakes

…base class one, or else it would never be called at all.
…ne, or else it would never be called at all.
…lass, also fix the default value of ClientCameraScript::startTarget to also match base class.
@pkubanek pkubanek merged commit f499907 into RTS2:master Sep 16, 2018
pkubanek pushed a commit that referenced this pull request Oct 23, 2018
…entially) lead to logic bugs (#35)

* Fix the signature of CommandStatusInfo::commandReturnFailed to match base class one, or else it would never be called at all.

* Fix the signature of SimbadTargetDb::printExtra to match base class one, or else it would never be called at all.

* Fix the type used for vector

* Fix the signature of Camera::checkQueChanges to match base class one, to avoid possible problems

* Fix the signature of DevClientCameraExec::startTarget to match base class, also fix the default value of ClientCameraScript::startTarget to also match base class.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants