I know its an old thread but i use protobuf3 with Java and it has the same
NPE behavior with .set(null-reference). Is their any chance to change this?
an option to generating java classes would be nice. It is absolutly
annoying to null-check on every .set method. This will lead to more errors
On Mon, Jun 8, 2015 at 7:43 AM, Colin Deasy cde...@demonware.net wrote:
Hey,
When reading
https://developers.google.com/protocol-buffers/docs/proto#simple I see a
stark warning indicating that Required is Forever advocating the use of
optional with additional application level validation
Right! Sorry for my lack of attention and thank you very much.
Best,
Felipe
2015-06-07 8:33 GMT-03:00 Mkhanyisi Madlavana mmadlav...@gmail.com:
The numbers
12 07 74 65 73 74 69 6e 67
are in the hexidecimal number system not in decimal number system. For
example 6e is a hexadecimal
Hey,
When reading
https://developers.google.com/protocol-buffers/docs/proto#simple I see a
stark warning indicating that Required is Forever advocating the use of
optional with additional application level validation routines. This is
because if at some point a required field is no longer
The numbers
12 07 74 65 73 74 69 6e 67
are in the hexidecimal number system not in decimal number system. For
example 6e is a hexadecimal equivalent for 110 in decimal number system. So
12 in hexadecimal is actually 0x12 which is 18 in decimal number system.
On Wednesday, June 3, 2015 at
I have a target which is old enough that it doesn't support thread local
variables. I'd like to build the protobuf3 libraries for it.
It looks like all I need to do is trigger arena.h and arena.cc to use the
version of thread_cache that is used by Android which
uses pthread_key_create. One
On Fri, Jun 5, 2015 at 7:02 PM, Austin Schuh austin.li...@gmail.com wrote:
I have a target which is old enough that it doesn't support thread local
variables. I'd like to build the protobuf3 libraries for it.
It looks like all I need to do is trigger arena.h and arena.cc to use the
version
Pull request sent. I felt a lot better putting the logic in
google/protobuf/stubs/platform_macros.h, so I put it there.
My platform is a very old version of Linux on an embedded box. I'm not
sure what to use for PLATFORM, but since I'm already re-creating the build
commands using bazel to
I have remade code so I now add into descriptor database all protofiles
specified by directory. There is but little problem with error handling.
From nature how I am handling errors it seems that message is possible to
decode but there is one error in error collector which is bothering me:
