Skip to content

fix docu #175

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.

Sign up for GitHub

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
flipflip8952 merged 1 commit into from
Dec 18, 2025
Merged

fix docu #175

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 0 additions & 7 deletions fpsdk_common/include/fpsdk_common/parser.hpp
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -131,13 +131,6 @@
*
* @image html parser.drawio.svg ""
*
* The parser implementation does not use any STL containers, templates or other c++ conveniences. Instead, low-level
* c-like types are used, in order to prevent any expensive heap (re)allocation and too much copying of data. For
* example, the returned ParserMsg contains a pointer to message rather than a std::vector<uint8_t>, and a const
* char* message name instead of a std::string. Applications can convert (copy) these easily to std::vector resp.
* std::string for further processing. Some of the utilities, such as fpsdk::common::parser::ubx::UbxMakeMessage(), do
* use STL containers for convenience.
*
* The maximum message size for each protocol is limited. For example, while the FP_B frame meta data would allow for
* messages up to 65'536 bytes, the parser discards any message larger than #fpsdk::common::parser::MAX_FP_B_SIZE.
* Messages larger than this are not practical and they do not (should not) exist. For example, it would take 5.6
Expand Down
Loading