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
New to this amazing lib, I'm very curious about the generated header of monster.fbs
add_name calls AddOffset(10, name);
add_inventory calls AddOffset(14, inventory);
I manually changed 14 to 12, and next color field from 16 to 12, everything works jsut fine!
and from the source code I read, AddOffset just PushElement of length sizeof(voffset_t), so there shouldn't be any problem with that.
And I print all the voffset_t in vtable offsets, field 12 is 0.
Forgive me if I missing something really obviously...
The text was updated successfully, but these errors were encountered:
If you look in the schema file, you'll see that the field at offset 12 in the vtable is a deprecated field. It is present in the vtable, but not in the object. If you go change these offsets, you'll break forwards/backwards compatability (see the "internals" document).
New to this amazing lib, I'm very curious about the generated header of monster.fbs
add_name calls AddOffset(10, name);
add_inventory calls AddOffset(14, inventory);
I manually changed 14 to 12, and next color field from 16 to 12, everything works jsut fine!
and from the source code I read, AddOffset just PushElement of length sizeof(voffset_t), so there shouldn't be any problem with that.
And I print all the voffset_t in vtable offsets, field 12 is 0.
Forgive me if I missing something really obviously...
The text was updated successfully, but these errors were encountered: