>
> you will have to create your own boolean fields if you need to track
> whether the optional is populated or not.
Other approach is to use *repeated* with <=1 element instead of *optional*.
Then had_foo() analogue will be (get_foo_size() != 0), presence flag and
the data will be kept wit
Hi,
I haven't been able to find any documentation that explicitly states
whether the wire (binary) format of Protobuf v2 messages are compatible
with protobuf messages generated with v3 (using `syntax=proto2`). The only
documentation seems to mention API differences between the two library
ver
Proto2 and proto3 are wire compatible. The same construct in proto2 and
proto3 will have the same binary representation. If your proto only uses
features available in both proto2 and proto3, systems built with proto2
should be able to communicate with systems built with proto3 without any
problem (
I am using (Windows 7) Eclipse IDE, Version: Luna Release (4.4.0) to build
a project. I am trying to use google protocol buffers. But I don't know how
to use protoc to compile .proto files and then how to use the source code
to build my project. I have downloaded compiler and source code from
I am using Eclipse IDE, Version: Luna Release (4.4.0) to build a project. I
am trying to use google protocol buffers. But I don't know how to use
protoc to compile .proto files and then how to use the source code to build
my project. I have downloaded compiler and source code from
https://deve
I am just using https://github.com/dcodeIO/ProtoBuf.js right now. I use it
for piping the internal protobuffer communication over websockets and it
just works like a charm.
Am Freitag, 26. Juni 2009 00:23:40 UTC+2 schrieb rthompson@gmail.com:
>
> Is there anything in the works that would al
