Re: [protobuf] Proto2 possible field options

2018-11-01 Thread Josh Humphries
On Thu, Nov 1, 2018 at 11:36 AM Michael Powell wrote: > On Thu, Nov 1, 2018 at 11:08 AM Josh Humphries > wrote: > > > > Michael, > > They map to field names in the options messages defined in > descriptor.proto. > > This is pretty interesting. So they've used the Proto spec to describe >

Re: [protobuf] Proto2 possible field options

2018-11-01 Thread Michael Powell
On Thu, Nov 1, 2018 at 11:08 AM Josh Humphries wrote: > > Michael, > They map to field names in the options messages defined in descriptor.proto. This is pretty interesting. So they've used the Proto spec to describe itself, ey? > Also, if you define custom options (by extending those options

Re: [protobuf] Proto2 possible field options

2018-11-01 Thread Josh Humphries
Michael, They map to field names in the options messages defined in descriptor.proto . Also, if you define custom options (by extending those options messages), you refer to them using qualified

[protobuf] Proto2 possible field options

2018-10-31 Thread Michael Powell
Hello, In the Proto2 specification, "field options" are sort of meta-tucked away. I don't think the specification really names them. Is there a list of them somewhere in the docs? i.e. field = label type fieldName "=" fieldNumber [ "[" fieldOptions "]" ] ";" fieldOptions = fieldOption { ","