I'd treat it like any other invalid pointer. Realistically I don't think we can come up with a way to treat these that would allow graceful compatibility if we were to actually introduce a new pointer type in the future.
-Kenton On Mon, Apr 22, 2019 at 10:07 AM Ian Denhardt <[email protected]> wrote: > The encoding spec mentions in the description of capability pointers > that values where B != 0 are reserved for future use, but doesn't > describe what an implementation not recognizing such a pointer should > do. What is the correct behavior here? > > -Ian > > -- > 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 [email protected]. > Visit this group at https://groups.google.com/group/capnproto. > -- 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 [email protected]. Visit this group at https://groups.google.com/group/capnproto.
