Skip to content

Commit 26b4cb8

Browse files
Fix type of type support type-erased data pointer
Signed-off-by: Christophe Bedard <[email protected]>
1 parent 51d3873 commit 26b4cb8

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

source/Tutorials/Advanced/Creating-An-RMW-Implementation.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -422,7 +422,7 @@ See `this example function <https://github.com/christophebedard/rmw_email/blob/f
422422
Publishers created by ``rclcpp`` will use C++ type support, while publishers created by ``rclpy`` will use C type support, since Python messages get converted into C messages.
423423
The ``/rosout`` publisher is managed by ``rcl``, which is written in C, so it uses C type support.
424424

425-
Then, using the concrete type support handle's type-erased pointer, ``const data *``, we get type support-specific information.
425+
Then, using the concrete type support handle's type-erased pointer, ``const void * data``, we get type support-specific information.
426426
For example, for C++ dynamic type support, this will be a ``const rosidl_typesupport_introspection_cpp::MessageMembers *``, which contains information about each field of the message.
427427
See `this example function <https://github.com/christophebedard/rmw_email/blob/f5e622bab24edaad8e0da054c7dbc698c6fb809c/rmw_email_cpp/src/conversion.cpp#L116-L153>`__, which extracts language-dependent type support information from the concrete type support handle.
428428
The information is used to read the type-erased message pointer and convert the message to a YAML object and then convert that to a string for the underlying middleware to publish.

0 commit comments

Comments
 (0)