constification of methods #15
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
when using C++, we often deal with std::string rather than "char*" thus, the device-name will often be passed as "s.c_str()", which really is a "const char*". to avoid warnings, it would be good if videoInput::getDeviceIDFromName() would accept "const char*". note: this probably breaks ABI compatibility! in this case it might be better to overload this member: int videoInput::getDeviceIDFromName(const std::string&name);
since the result of getDeviceName() is really a pointer to a static array, the caller should (must) never change these values. they should therefore declared "const".
|
thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
methods handling with device-names should really use
const char*for the device names (both as an argument and as a result)