Could you describe the issues you have when compiling protobuf on Mac?
On Thursday, March 17, 2016 at 2:09:05 PM UTC-7, Sidney Lu wrote:
>
> Suffer this for a couple of weeks
> any suggestions are respectful
>
--
You received this message because you are subscribed to the Google Groups
"Protoco
Thanks for the suggestion but this would mean that every message would need
to be packed in this structure including nested messages. It's simply too
much for a hack for what I believe was a simple and useful feature that was
part of proto2 and removed with no explanation or way to disable it.
On
On Tuesday, March 15, 2016 at 12:32:07 PM UTC-7, Jeremy Ong wrote:
>
> Hi google pb,
>
> I was wondering if an interface exists for specifying that I do not want
> the proto3 serialization or deserialization to discard unknown fields. My
> understanding was that this change was made from proto2
Neither are appropriate in my use case unfortunately. I want to be
able to tag any message with data in a field range special within the
organization. The point is that I don't want to add fields to the
existing hundreds and hundreds of message types we have already.
For the time being, I have swi
You can do something like this by serializing the normal message and the
added fields separately and then concatenating the byte strings.
Not helpful if you need to do this above the byte string level. And may
have other disadvantages, e.g., extra copies ...
On Fri, Mar 18, 2016 at 6:51 PM, Jerem
On Tuesday, March 15, 2016 at 12:32:07 PM UTC-7, John Coffey wrote:
>
> I wrote a C++ gRPC application using the latest protobuf master code base.
> The application is an RPC application that supports a couple of custom
> Message types (using protoc3 as required by gRPC)
>
> One of these fiel
