Skip to content

Make processRTCMframe weak #147

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Aug 1, 2022

Conversation

LeeLeahy2
Copy link
Contributor

Allow processRTCMframe to be overridden. Its replacement would now be
able to place all of the bytes into a buffer for processing at a later
time and eliminate a deep call stack for every byte.

PaulZC and others added 2 commits July 29, 2022 10:11
Allow processRTCMframe to be overridden.  Its replacement would now be
able to place all of the bytes into a buffer for processing at a later
time and eliminate a deep call stack for every byte.
@PaulZC
Copy link
Collaborator

PaulZC commented Aug 1, 2022

Hi Lee (@LeeLeahy2 ),

Many thanks for the update. It's failing on ESP32 (v2.0.4)... "error: value computed is not used" on *rtcmFrameCounter++;. (Previously this would have been a warning, but v2.0.4 now treats it as an error...) I'll merge it into release_candidate and fix it there.
I'm also going to rename the SentenceTypes. If they're public, we need to make their names much less generic or we will hit compiler errors with other libraries at some point.
Cheers!
Paul

@PaulZC PaulZC changed the base branch from main to release_candidate August 1, 2022 10:23
@PaulZC PaulZC merged commit cc6fe31 into sparkfun:release_candidate Aug 1, 2022
@PaulZC
Copy link
Collaborator

PaulZC commented Aug 1, 2022

Hi Lee (@LeeLeahy2 ),

Please pull release_candidate and give it a quick test. If you're happy, we can get this merged and up-issued.

Thanks!
Paul

@LeeLeahy2
Copy link
Contributor Author

Hi Paul,

This looks good.

Thanks,
Lee

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.

2 participants