Hello, I'd like to get a handle on an identification strategy for elements in a Protocol Buffer descriptor hierarchy and just trying to get a sense of what is involved.
My parser is working well. I decided to take an approach through Antlr4 for dotnet and CSharp after all. .<package-path/>.<element-path/>.<item-ident/> Where <element-path/> is some combination of items, such as messages, enumerations, and <item-ident/> is a terminal item, such as options, enumerated fields, and so on. I am focused on the v2 specification, however, this may be applicable to v3 as well, though the specific protos I am interested in are currently presented in the v2 version. http://developers.google.com/protocol-buffers/docs/reference/proto2-spec I'm thinking that the whole Identification strategy need to be stronger than language level String, for instance, in order to best align with a path through an AST tree, but I'd be curious what insights others are willing to share. Cheers, and thanks in advance for any insights, Michael W Powell -- 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 protobuf+unsubscr...@googlegroups.com. To post to this group, send email to protobuf@googlegroups.com. Visit this group at https://groups.google.com/group/protobuf. For more options, visit https://groups.google.com/d/optout.
