100 isn't "non-standard" as such, and shouldn't cause anything to fail. What exactly are you seeing?
The valid range is 1-536870911, omitting 19000-19999 (and any reserved areas in your specific messages) smaller numbers are cheaper (fewer bytes) to encode, so are usually preferred - but: that's it. I'm guessing you're actually using some non-compliant code that is assuming field-headers are single bytes? That is true for very low field numbers (4 bytes, so: 1-15), but field 100 will take two bytes for the header. Is that the problem here? On Thu, 7 Jan 2021, 22:00 peo stri tise safe, <[email protected]> wrote: > What is the purpose of setting starting index values for a GPB message > definition to something other than 1? I am seeing a value of 100 in a > particular application and it is causing the encoding of the message to > fail. Just wondered why the use of values other than 1 for the first item > in the message. > > -- > You received this message because you are subscribed to the Google Groups > "Protocol Buffers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/protobuf/957aae3b-32f8-4d9d-8f5f-732e26e08cedn%40googlegroups.com > <https://groups.google.com/d/msgid/protobuf/957aae3b-32f8-4d9d-8f5f-732e26e08cedn%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/protobuf/CAF95VAzHudaTfHndUOVbYKGV2finmioPLQxwcSHFVWs9NHgSNw%40mail.gmail.com.
