Quoting n...@8thwall.com (2018-02-21 13:39:06)
> Per capnp "evolving your schema" we tried changing the name of a struct
> but keeping its id the same e.g. changing this:
> struct MyMessageList {
> mList @0: List(MyMessage);
> }
> struct MyMessage {
> field0 @0: Int32;
> }
> to this:
> struct MyMessageList {
> mList @0: List(DeprectedMyMessage);
> }
> struct DeprectedMyMessage @0xd4201303ceef0b19� {
> field0 @0: Int32;
> }
> We found that the generated header files were the same (modulo the name
> change), but that the data section in the c++ files had changed values,
> which was worrisome. For example:
>
> ...IIRC, the generated code embeds the (serialized) schema, which can be used for things like encoding to JSON, or the reflection API. The change you've made shouldn't affect the (binary) wire format at all. -- You received this message because you are subscribed to the Google Groups "Cap'n Proto" group. To unsubscribe from this group and stop receiving emails from it, send an email to capnproto+unsubscr...@googlegroups.com. Visit this group at https://groups.google.com/group/capnproto.
signature.asc
Description: signature
