From e9140b867e0e48df002973c2b3804787acb0e1ad Mon Sep 17 00:00:00 2001 From: "mergify[bot]" <37929162+mergify[bot]@users.noreply.github.com> Date: Thu, 19 Dec 2024 08:39:28 +0100 Subject: [PATCH] Remove wrong comments (backport #240) (#242) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Remove wrong comments (#240) (cherry picked from commit 246e57ee601d65e81a2c29d0f2e9bfa0eb66fc26) Co-authored-by: Christoph Fröhlich --- include/realtime_tools/realtime_buffer.hpp | 5 ----- include/realtime_tools/realtime_clock.hpp | 5 ----- 2 files changed, 10 deletions(-) diff --git a/include/realtime_tools/realtime_buffer.hpp b/include/realtime_tools/realtime_buffer.hpp index 78c320fa..cad69db7 100644 --- a/include/realtime_tools/realtime_buffer.hpp +++ b/include/realtime_tools/realtime_buffer.hpp @@ -27,11 +27,6 @@ // POSSIBILITY OF SUCH DAMAGE. /* - * Publishing ROS messages is difficult, as the publish function is - * not realtime safe. This class provides the proper locking so that - * you can call publish in realtime and a separate (non-realtime) - * thread will ensure that the message gets published over ROS. - * * Author: Wim Meeussen */ diff --git a/include/realtime_tools/realtime_clock.hpp b/include/realtime_tools/realtime_clock.hpp index 2ff9bf4c..6be35449 100644 --- a/include/realtime_tools/realtime_clock.hpp +++ b/include/realtime_tools/realtime_clock.hpp @@ -27,11 +27,6 @@ // POSSIBILITY OF SUCH DAMAGE. /* - * Publishing ROS messages is difficult, as the publish function is - * not realtime safe. This class provides the proper locking so that - * you can call publish in realtime and a separate (non-realtime) - * thread will ensure that the message gets published over ROS. - * * Author: Wim Meeussen */