Will the C# implementation support proto2 messages?
What is the capability story? I assume the wire format is compatible if no
proto3 exclusive features are used?
On Tuesday, August 4, 2015 at 5:43:36 AM UTC-7, Jon Skeet wrote:
> That looks like you're expecting a protobuf.net-style approach - t
- I am using protobuf-2.6.1
- OS is solaris 5.11 (SunOS 5.11 11.2 sun4v sparc SUNW,T5240)
- configure para: ./configure --disable-64bit-solaris
--prefix=/home/jyao1/proto CC=/opt/swt/install/gcc-4.9.2/bin/gcc
- protobuf library build successfully
- However, i got the following errors for my app
U
Will the C# implementation support proto2 message as well?
What is the compatibility story between proto2 and proto 3? I assume the
wire format is compatible as long as no proto 3 exclusive features are used.
On Tuesday, August 4, 2015 at 5:43:36 AM UTC-7, Jon Skeet wrote:
> That looks like you'
On Fri, Oct 9, 2015 at 10:51 AM, Walter Schulze
wrote:
> In other words C# and those new languages won't be able to serialize the
> descriptor?
>
descriptor.proto is an exception. It's allowed to be imported by proto3
files to support custom options. I.e., the following is explicitly allowed:
syn
In other words C# and those new languages won't be able to serialize the
descriptor?
On 9 October 2015 at 19:44, 'Feng Xiao' via Protocol Buffers <
protobuf@googlegroups.com> wrote:
> The decision is not to support proto2 in C# (and probably also for all
> other languages that are new in v3.0.0+)
The decision is not to support proto2 in C# (and probably also for all
other languages that are new in v3.0.0+).
On Fri, Oct 9, 2015 at 10:42 AM, Teddy Zhang wrote:
> Will the C# implementation support proto2 message as well?
> What is the compatibility story between proto2 and proto 3? I assume
