refactor orb: uORB::Manager is responsible for the DeviceMaster objects
This has the following benefits: - Manager can ensure that there is at most one instance of DeviceMaster per Flavor - The Manager needs access to (static) data of DeviceMaster already. This will make it easier to access this data in a non-static way, and does not introduce new dependencies.
Showing
- src/modules/uORB/uORBCommon.hpp 4 additions, 2 deletionssrc/modules/uORB/uORBCommon.hpp
- src/modules/uORB/uORBDevices_nuttx.hpp 3 additions, 0 deletionssrc/modules/uORB/uORBDevices_nuttx.hpp
- src/modules/uORB/uORBDevices_posix.hpp 3 additions, 0 deletionssrc/modules/uORB/uORBDevices_posix.hpp
- src/modules/uORB/uORBMain.cpp 2 additions, 10 deletionssrc/modules/uORB/uORBMain.cpp
- src/modules/uORB/uORBManager.cpp 36 additions, 0 deletionssrc/modules/uORB/uORBManager.cpp
- src/modules/uORB/uORBManager.hpp 11 additions, 0 deletionssrc/modules/uORB/uORBManager.hpp
Please register or sign in to comment