You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
struct members are serialized in the order defined in fpp
no padding
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.
The text was updated successfully, but these errors were encountered:
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:
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.
The text was updated successfully, but these errors were encountered: