Skip to content

Conversation

@sfe-SparkFro
Copy link
Collaborator

@PaulZC This is the new structure that @gigapod and I discussed. This will allow us to separate features that are supported on different modules, such as audio and GNSS, more easily and portably than virtual inheritance. I've only done the audio so far, but I tested this with the LARA-R6 nd it works fine. If all looks good, I'll work on doing the same with other features (mainly just pulling them out of the base class).

Audio class (and other feature sets) now uses templating instead of virtual inheritance
Copy link
Member

@gigapod gigapod left a comment

Choose a reason for hiding this comment

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

Overall looks awesome - glad it's working.

And solid - fast - hacking at this!

@gigapod
Copy link
Member

gigapod commented Nov 30, 2023

One other comment I had here - for the internal classes/templates, can we move to a CamelCase class name, not the YELLING_AT_YOU format? Minor, but more approachable and modern.

@sfe-SparkFro sfe-SparkFro mentioned this pull request Dec 4, 2023
@sfe-SparkFro
Copy link
Collaborator Author

One other comment I had here - for the internal classes/templates, can we move to a CamelCase class name, not the YELLING_AT_YOU format? Minor, but more approachable and modern.

Agreed, will fix the code style once the architecture is finalized, was just picking some names to be able to move forward. Tracking this in #9

@sfe-SparkFro sfe-SparkFro merged commit 1ab5265 into v1.0.0 Dec 4, 2023
@sfe-SparkFro sfe-SparkFro deleted the template_structure branch December 4, 2023 16:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants