Comment #7 on issue 515 by peterhan...@yahoo.com: More intelligent enums
http://code.google.com/p/protobuf/issues/detail?id=515
The proposed solution doesn't work because:
1. The name of the enum type is changed from "Foo" to "Foo::Enum" which
will be confusing to the users.
The proposal te
On Fri, Jan 31, 2014 at 4:36 AM, wrote:
>
> Comment #7 on issue 515 by peterhan...@yahoo.com: More intelligent enums
> http://code.google.com/p/protobuf/issues/detail?id=515
>
> The proposed solution doesn't work because:
>>> 1. The name of the enum type is changed from "Foo" to "Foo::Enum" whic
Comment #7 on issue 570 by getae...@gmail.com: build 2.4.1 failed on mac os
x 10.9
http://code.google.com/p/protobuf/issues/detail?id=570
"Adding #include " solution worked for me
--
You received this message because this project is configured to send all
issue notifications to this addre
>
> how u have decodeed first mesage?
neded help
--
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 g
Hi,
I'm trying to compile one of Chrome's proto files:
https://chromium.googlesource.com/experimental/chromium/src/+/master/sync/protocol/sync_enums.proto
using exe from "protoc-2.5.0-win32.zip"
and I get the following error:
"sync_enums.proto:13:8: Option "retain_unknown_fields" unknown"
Anybod
On Thu, Jan 30, 2014 at 6:56 AM, Ik Si wrote:
> Hi,
>
> I'm trying to compile one of Chrome's proto files:
>
> https://chromium.googlesource.com/experimental/chromium/src/+/master/sync/protocol/sync_enums.proto
> using exe from "protoc-2.5.0-win32.zip"
> and I get the following error:
>
> "sync_e