Oh, huh, good to know. Sorry for the misinformation Constantine.
On Mon, Jun 7, 2010 at 9:02 PM, Kenton Varda wrote:
> Actually, UnknownFieldSet is exactly where the custom options will end up
> if their definitions are not compiled into the binary. DescriptorPool
> converts all UninterpretedOp
Actually, UnknownFieldSet is exactly where the custom options will end up if
their definitions are not compiled into the binary. DescriptorPool converts
all UninterpretedOptions into either extensions or unknown fields when
building the descriptors.
The way to access them is to take the FieldOpti
Hm. Can you send the code snippet you are using to try to access your custom
option? You should just be accessing the options proto from
FieldDescriptor::options(), and calling GetExtension() on that.
Also, UnknownFields doesn't have anything to do with options extensions. Did
you mean Uninterpret
Hello,
I'm curious is there any way to access extension fields for
FieldOptions(or MessageOptions) in DynamicMessage?
i.e.
We define message and option, like this:
extend google.protobuf.FieldOptions {
optional string my_opt = 50001;
}
message MyMessage {
required string my_field [(my_
