RTC Toolkit 6.0.0
Loading...
Searching...
No Matches

Implementation of the DdsWaitSet. More...

#include "ddsReaderListener.hpp"
#include "rtctk/telSub/ddsWaitSet.hpp"
#include "rtctk/telSub/ddsWaitSetIf.hpp"
#include "rtctk/componentFramework/exceptions.hpp"
#include "rtctk/componentFramework/logger.hpp"
#include "ciiException.hpp"
#include <cassert>
#include <fastdds/dds/core/Types.hpp>
#include <fmt/core.h>
#include <limits>
#include <system_error>
#include <variant>
#include "fastdds/utils/IPLocator.hpp"

Classes

struct  DdsReaderParams
 Structure that keeps together topic name and DDS Data Writer listener. More...
 
class  DdsSub
 All functionality needed to create DDS entities for DDS data subscribing is concentrated in this class. More...
 
class  InvalidArgumentException
 Thrown if an argument passed to a method was invalid. More...
 
class  RtctkException
 The RtctkException class is the base class for all Rtctk exceptions. More...
 

Namespaces

namespace  rtctk
 
namespace  rtctk::telSub
 

Functions

log4cplus::Logger & GetLogger (const std::string &name="app")
 Get handle to a specific logger.
 

Detailed Description

Implementation of the DdsWaitSet.

Function Documentation

◆ GetLogger()

log4cplus::Logger & rtctk::componentFramework::GetLogger ( const std::string & name = "app")

Get handle to a specific logger.

This is used all over the place together with the log4cplus logging macros.

The default logger is retrieved when calling GetLogger() without any further arguments

Instrument RTC developers are supposed to either use:

  • the main application logger e.g. GetLogger(), or Getlogger("app")
  • custom childloggers of the main application logger e.g. GetLogger("app.foobar")

The RTC Toolkit will use a different logger hierarchy, namely:

  • the main rtctk logger e.e. GetLogger("rtctk")
  • specific child loggers of the main rtctk logger e.g. GetLogger("rtctk.foobar")
Parameters
nameoptional: name of the requested logger
Returns
handle to the requested logger