Good news: There was a patch for this submitted to the internal version of
the code which should make its way to SVN today or tomorrow, and will be in
the 2.0.3 release.
On Wed, Nov 19, 2008 at 1:29 AM, Jerry Cattell <[EMAIL PROTECTED]>wrote:
>
> I'm trying to use a custom EnumValueOption:
>
>
> package test;
>
> import "google/protobuf/descriptor.proto";
> extend google.protobuf.EnumValueOptions {
> optional string code = 1234;
> }
>
> enum ProductType {
> ROCK = 0 [(code) = "R"];
> PAPER = 1 [(code) = "P"];
> SCISSORS = 2 [(code) = "S"];
> }
>
>
> However, this doesn't seem to parse:
> test.proto:9:12: Expected ";".
> test.proto:10:13: Expected ";".
> test.proto:11:16: Expected ";".
>
> Looking at unittest_custom_options.proto, it mentions a TODO for
> this. Are custom EnumValueOptions currently supported? If not, any
> idea when they will be?
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Protocol Buffers" group.
To post to this group, send email to protobuf@googlegroups.com
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
-~----------~----~----~----~------~----~------~--~---
