[protobuf] Re: [protobuf-team] Protobuf and Abseil in Debian/Ubuntu

There's also header dependency issue, i.e. libprotobuf-dev may distribute headers which may transitively include headers from libabseil-dev (currently we duplicate atomicops, platform macros, etc). This means the protobuf dev package needs to pin with a specific libabseil-dev, even if we go with

[protobuf] 3.4.0 released

Please see the release page for details. Thanks, Jisi -- 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

Re: [protobuf] Protobuf member by member copy from java to protobuf class and vice versa

Usually it's recommended to just use the protobuf generated objects as in-memory model. Or you can embed the proto message objects in your other Java classes. Is there any specific reason this doesn't work for you? On Wed, Aug 9, 2017 at 4:43 AM Jay Sharma wrote: > I

Re: [protobuf] Protobuf in python during message deserialization complains about 'Unexpected end-group tag.'

ParseFromString only takes the binary string that SerializeToString() generates. I don't know you get the input bytes, but you probably would have to decode it first. On Fri, Jun 30, 2017 at 6:45 AM Tanmay Saha wrote: > This is what I have done. > > mymessageobj =

Re: [protobuf] Accessing repeated oneof fields in Java

There's no such API. You would need to write a loop to find a match. On Tue, Jun 27, 2017 at 12:17 PM Steven Seeley wrote: > > 3:05 PM (less than a minute ago) > Hi guys, > > I've been trying to implement a means to compare two different protobuf > messages using a mapping

Re: [protobuf] Maps and append-as-merge; expectation clarification please

Yes. It will replace the value with the same key. On Sat, Jun 24, 2017 at 11:08 AM Marc Gravell wrote: > Basically, if I have > > message Foo { > int32 x = 1; > int32 y = 2; > } > message Bar { > map items = 1; > } > > And I serialize 2 fragments

[protobuf] Proto3 preserve unknowns

Hi, We are planning to bring unknowns fields back into proto3. Note this will change the behavior for all the proto3 users. Please read the doc about detailed plans. Feel free to comment on the #272

[protobuf] Make C++ implementation C++11 only.

C++11 has been out for several years and we are thinking of moving to allow C++11 features from being used in the code base. That means the implementation will not be able to compile if you don't have a C++11 compiler. We may create a branch that works for C++98. The branch will only accept bug

Re: [protobuf] c++ singleton support

Each message type has a default instance. You can specify the default values for the fields in the message and use the default instance of that message as the singleton. On Sat, Dec 3, 2016 at 9:13 PM 梅骁 wrote: > Hi, > Does protobuf has singleton support? I want to use

Re: [protobuf] Currency/Monetary amount in Protobuf

There's no native support for MonetaryAmount. However, you can define a message to represent the type with the precision and write a custom tool to convert the message to and from the native Java type. On Sun, Dec 4, 2016 at 4:29 PM Luis Trigueiros wrote: > Hi, > > I

Re: [protobuf] Any script or tool to check forward/backward compatibility breaking changes to protobuf IDL?

I heard this feature requests several times, but I'm not aware if anyone has implemented it yet. Please post it back if you end up implanting the tool. On Tue, Dec 6, 2016 at 10:26 PM Ajay wrote: > Hi, > > Are you guys aware of any tool or script that can be used to check

Re: [protobuf] is it possible to compile protobuf 3.0 on windows? (protobuf)

Could you elaborate on the pthread issue? It should work for msvc 2015. On Wed, Dec 7, 2016 at 2:52 PM lucidbee wrote: > I may be missing something obvious. > > I am trying to compile protobuf 3.0.0.2 on windows 10 using msvs 2015 > update 3. > > Using cmake. > > Seems like

Re: [protobuf] Protobuf / Java / ParseFrom inconsistent behavior

Parsing the bytes from a valid protobuf wireformat into a unmatched type shouldn't cause parsing failures. Those unrecognized fields should be kept in the unknown fields and should be able to serialize back. Java implementation enforces roundtrip to be lossless. I'm not familiar with the Go

Re: [protobuf] Protocol Version 2.1.0 available for download...?

It's no longer available for download. You probalby would have to checkout the github ref: https://github.com/google/protobuf/commit/1fb3d394e5bb4ded7a76dc8d44a701733aad3553 and build from there. On Fri, Dec 9, 2016 at 6:03 AM Srinivas DGS wrote: > Hi All, > > Can

[protobuf] 3.0.0 released

Please see the release page for details. Thanks, Jisi -- 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