component.h File Reference

#include <memory>
#include <utility>
#include <vector>
#include "cyber/base/macros.h"
#include "cyber/blocker/blocker_manager.h"
#include "cyber/common/global_data.h"
#include "cyber/common/types.h"
#include "cyber/common/util.h"
#include "cyber/component/component_base.h"
#include "cyber/croutine/routine_factory.h"
#include "cyber/data/data_visitor.h"
#include "cyber/scheduler/scheduler.h"

Include dependency graph for component.h:

This graph shows which files directly or indirectly include this file:

Go to the source code of this file.

Classes
class	apollo::cyber::Component< M0, M1, M2, M3 >
	The Component can process up to four channels of messages. The message type is specified when the component is created. The Component is inherited from ComponentBase. Your component can inherit from Component, and implement Init() & Proc(...), They are picked up by the CyberRT. There are 4 specialization implementations. More...
class	apollo::cyber::Component< NullType, NullType, NullType, NullType >
class	apollo::cyber::Component< M0, NullType, NullType, NullType >
class	apollo::cyber::Component< M0, M1, NullType, NullType >
class	apollo::cyber::Component< M0, M1, M2, NullType >

Namespaces
	apollo
	PlanningContext is the runtime context in planning. It is persistent across multiple frames.
	apollo::cyber

Macros
#define	CYBER_REGISTER_COMPONENT(name)   CLASS_LOADER_REGISTER_CLASS(name, apollo::cyber::ComponentBase)

Macro Definition Documentation

CYBER_REGISTER_COMPONENT

#define CYBER_REGISTER_COMPONENT

(

name

)

CLASS_LOADER_REGISTER_CLASS(name, apollo::cyber::ComponentBase)