Why do you need to generate different code for the two? All the official code generators generate exactly the same code for message classes whether they be nested messages or groups. Version 1 of protocol buffers generated different classes and it proved to be an enormous pain.
On Thu, Apr 29, 2010 at 2:04 PM, Adam Kwintkiewicz < [email protected]> wrote: > hmm this is a slight problem. I am iterating over the nested messages and > then generating a message/group code. I don't have reference to the specific > field > > 2010/4/29 Kenton Varda <[email protected]> > > A single message type can be used as both a message and as a group, so >> there is no way to tell which it is from the Descriptor. You have to have >> the FieldDescriptor in the containing message. >> >> >> On Thu, Apr 29, 2010 at 1:36 PM, adamdms <[email protected]>wrote: >> >>> how to check whether the current message (Descriptor *) is a group? >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Protocol Buffers" group. >>> To post to this group, send email to [email protected]. >>> To unsubscribe from this group, send email to >>> [email protected]<protobuf%[email protected]> >>> . >>> For more options, visit this group at >>> http://groups.google.com/group/protobuf?hl=en. >>> >>> >> > -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
