Skip to content
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

Document autocoded serialization and deserialization #646

Open
zimri-leisher opened this issue Mar 3, 2025 · 0 comments
Open

Document autocoded serialization and deserialization #646

zimri-leisher opened this issue Mar 3, 2025 · 0 comments

Comments

@zimri-leisher
Copy link

zimri-leisher commented Mar 3, 2025

The behavior of the autocoded ser/deser functions for structs/arrays/enums should be well-defined and guaranteed not to change.
As discussed with @bocchino , for serialization, the definition should be:

  1. struct members are serialized in the order defined in fpp
  2. no padding
  3. big endianness

Additionally, notes should be made about potentially ambiguous serialization behavior for types like Fw::String and the various buffer types. It should be made clear that serializing a primitive type (int, float or char) behaves exactly as you'd expect.

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

No branches or pull requests

1 participant