On Sat, Feb 2, 2013 at 12:37 PM, Roman Simakov <[email protected]>wrote:
> Thanks, > > 2013/2/2 Oliver Jowett <[email protected]>: > > Fields don't have to be encoded in any particular order, so you can have > a > > valid message encoding where the encoding of 'eom' is followed by other > > fields. > > I.e. I cannot be sure eom is the last field? > That's right. With the standard implementation I think you will most commonly hit this if you happen to re-encode a message that contains unknown fields. More generally, see https://developers.google.com/protocol-buffers/docs/encoding#order (short version: writing fields in order is preferred because parsers may optimize for this, but writing them out of order is still valid) Oliver -- 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 post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/protobuf?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
