On Sun, Jan 13, 2013 at 3:34 PM, Oliver Jowett wrote:
> This seems like a function that would be only useful for your specific
> requirement. It would be no use, for example, in any situation where
> backwards message compatibility is needed.
>
Even with backward message compatibility, you might
On Sun, Jan 13, 2013 at 12:04 PM, Klaim - Joël Lamotte
wrote:
>
> On Sun, Jan 13, 2013 at 9:54 AM, Feng Xiao wrote:
>>
>>
>> With protobuf reflection you can easily write a function to check if all
>> fields of a message are set.
>>
>
> I see, thanks for pointing that, it's a good alternative.
>
On Sun, Jan 13, 2013 at 9:54 AM, Feng Xiao wrote:
>
> With protobuf reflection you can easily write a function to check if all
> fields of a message are set.
>
>
I see, thanks for pointing that, it's a good alternative.
But wouldn't it be far more efficient if it was generated by protobuf in
the
On Sat, Jan 12, 2013 at 1:35 AM, Klaim - Joël Lamotte wrote:
>
>
>
> On Fri, Jan 11, 2013 at 6:01 PM, Feng Xiao wrote:
>
>> Have a look at protobuf reflection API here:
>>
>> https://developers.google.com/protocol-buffers/docs/reference/cpp/google.protobuf.message
>> You also need to know about d
On Fri, Jan 11, 2013 at 6:01 PM, Feng Xiao wrote:
> Have a look at protobuf reflection API here:
>
> https://developers.google.com/protocol-buffers/docs/reference/cpp/google.protobuf.message
> You also need to know about descriptors to use reflection:
>
> https://developers.google.com/protocol-bu
Have a look at protobuf reflection API here:
https://developers.google.com/protocol-buffers/docs/reference/cpp/google.protobuf.message
You also need to know about descriptors to use reflection:
https://developers.google.com/protocol-buffers/docs/reference/cpp/google.protobuf.descriptor
On Fri,
