Back in 2015, the ROS2 rules for the names of fields in topic and services were tightened up to disallow uppercase characters (and hence camel case). The original discussion seems to have been here:
https://groups.google.com/forum/#!msg/ros-sig-ng-ros/YAyfgrvUvs0/ULthxTF51GwJ
with the follow-up PR done here:
https://github.com/ros2/rosidl/pull/25
Since then, some users of ROS2 have expressed a desire to loosen these restrictions, and put the rules back to what they were in ROS1 (allowing camel case, among other things). I'm interested in hearing opinions from the community on whether the restrictions are beneficial, harmful, or don't matter very much. Thoughts welcome!
---
[Visit Topic](
https://discourse.ros.org/t/relaxing-ros2-topic-service-field-name-restrictions/6371/1) or reply to this email to respond.
If you do not want to receive messages from ros-users please use the unsubscribe link below. If you use the one above, you will stop all of ros-users from receiving updates.
______________________________________________________________________________
ros-users mailing list
ros-users@lists.ros.org
http://lists.ros.org/mailman/listinfo/ros-users
Unsubscribe: <
http://lists.ros.org/mailman//options/ros-users>
(text/plain)