AP_Baro: adjust handling of instance/driver arrays to use ARRAY_SIZE … #31300
Conversation
This file contains hidden or 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
…and iterator if you are about to index something, directly use its size for your sanity check. Or avoid the check altogether by using an iterator.
|
A trivial follow-up PR will remove BARO_MAX_DRIVERS and just use BARO_MAX_INSTANCES everywhere. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
…and iterator
if you are about to index something, directly use its size for your sanity check.
Or avoid the check altogether by using an iterator.
Tested on a Pixhawk6X with a Here4 GPS and its two internal baros. No change in behaviour vs master