You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't see why the IP address in the different client init functions shouldn't be const. I'm having to fix it in my code and there's a hack in joint_trajectory_interface.cpp:60 which also painfully addresses it.
2 participants
JeremyZoss commented 7 days ago
Agreed. There are many other areas in the core libraries that could probably be improved for const-correctness. But these things kind of have a way of cascading to make small changes trigger much larger changes. So, I agree in theory, but we may need to be selective about what code is updated to prevent potentially breaking higher-level code that builds on these libraries.
The text was updated successfully, but these errors were encountered:
connection.init(char ) => .init(const char)
I don't see why the IP address in the different client init functions shouldn't be const. I'm having to fix it in my code and there's a hack in joint_trajectory_interface.cpp:60 which also painfully addresses it.
2 participants
JeremyZoss commented 7 days ago
Agreed. There are many other areas in the core libraries that could probably be improved for const-correctness. But these things kind of have a way of cascading to make small changes trigger much larger changes. So, I agree in theory, but we may need to be selective about what code is updated to prevent potentially breaking higher-level code that builds on these libraries.
The text was updated successfully, but these errors were encountered: