Skip to content

lola: Move SkeletonAndServiceElements component code to subdir and split up bazel targets - #1023

Draft
bemerybmw wants to merge 6 commits into
mainfrom
brem_skeleton_unit_design
Draft

lola: Move SkeletonAndServiceElements component code to subdir and split up bazel targets#1023
bemerybmw wants to merge 6 commits into
mainfrom
brem_skeleton_unit_design

Conversation

@bemerybmw

Copy link
Copy Markdown
Contributor

No description provided.

The new architectural design introduced a new set of units and
components. Eventually, the code structure should more or less follow
the design. As a first step, we move the classes corresponding to the
lola SkeletonAndServiceElements component into a new subdirectory. We
may decide later to further divide the code into one directory per unit.
namespace score::mw::com::impl::lola
{

class ILolaSkeleton

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add documentation to class and also all functions in interfaces.

/// \return A pair containing:
/// - An type erased pointer to the allocated data storage (void*).
/// - The EventDataControlComposite for managing the event's control data.
virtual GenericRegistrationResult RegisterGeneric(const ElementFqId element_fq_id,

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Signature will slightly change with my type-erasure PR ... then we will only have a Register (because there is no GenericEvent/Field anymore)

tags = ["FFI"],
visibility = [
"//score/mw/com/impl/bindings/lola:__pkg__",
"//score/mw/com/impl/bindings/lola:__subpackages__",

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do we have still the methods dir? It shall beall in skeleton_and_service_elements?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Backlog

Development

Successfully merging this pull request may close these issues.

2 participants