Closed Kukanani closed 7 years ago
See 2.3 of http://wiki.ros.org/ROS/Patterns/Conventions.
This change improves ROS2 compatibility. Because of how ROS2 message headers are generated, the following behavior arises:
Detection3DArray.msg -> vision_msgs/msg/detection3_d_array.hpp Detection3dArray.msg -> vision_msgs/msg/detection3d_array.hpp
The second line makes more sense and is preferable.
Note: Legacy messages such as geometry_msgs/Pose2D only use a capital D to ensure backwards-compatibility.
geometry_msgs/Pose2D
After talking with people at OSRF, it's probably best to stick with convention, despite the awkward include.
See 2.3 of http://wiki.ros.org/ROS/Patterns/Conventions.This change improves ROS2 compatibility. Because of how ROS2 message headers are generated, the following behavior arises:
The second line makes more sense and is preferable.
Note: Legacy messages such asgeometry_msgs/Pose2D
only use a capital D to ensure backwards-compatibility.