fixed nh.getParam template with gcc-arm-none-eabi #587
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
with the following code:
```cpp
template <typename T>
static inline T get_single_param_(const char *param_name, T default_value)
{
std::array<T, 1> buf;
if (nh.getParam(param_name, buf.data())) {
return buf[0];
} else {
return default_value;
}
}
```
Under rp2040 (arm-none-eabi-gcc, 32bit), if T is "int", gcc will convert
the int to "short int" thus failing compilation.
Using "int32_t" for T didn't help, and fundamentally it's a problem of
"int" not being really cross-platform.
Changing the "int" in rosserial_client to "int32_t" fixed the issue.
Ultimately, all "int" in the codebase should be "int32_t" including
message_generation, but that would be a breaking change.
Even this change might be breaking for some codes.
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.
with the following code:
Under rp2040 (arm-none-eabi-gcc, 32bit), if T is "int", gcc will convert
the int to "short int" thus failing compilation.
Using "int32_t" for T didn't help, and fundamentally it's a problem of
"int" not being really cross-platform.
Changing the "int" in rosserial_client.h to "int32_t" fixed the issue.
Ultimately, all "int" in the codebase should be "int32_t" including
message_generation, but that would be a breaking change.
Even this change might be breaking for some codes.