| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
Swift generators should default to CamelCasing the proto package and prefixing
symbols with that, but this option allows developers to override that behavior
with something custom if they desire.
Fixes https://github.com/google/protobuf/issues/1833
|
|\
| |
| | |
Integrated internal changes from Google
|
| |
| |
| |
| |
| |
| | |
This seems to be necessary to prevent warnings in some compiler
configurations, particularly for tag numbers that are too large to fit
in a signed 32-bit int.
|
| | |
|
| |\ |
|
| | | |
|
| |/
|/|
| |
| |
| |
| |
| | |
Behavior of define GOOGLE_PROTOBUF_NO_STATIC_INITIALIZER has been
altered between 337a028 and cc8ca5b for C++.
See github issue #2385 for further details.
|
| |
| |
| | |
Some compiler will report: 'error: integer constant is too large for long type'
|
| |
| |
| |
| | |
In php, class name cannot be "Empty". Modified code generator to (#2375) generate GPBEmpty instead (for google.protobuf.Empty only). Also change
runtime code to work with the new generated code accordingly.
|
|\ \
| | |
| | | |
Add missing include in message_lite.cc
|
| | |
| | |
| | |
| | |
| | | |
This changes fixes "use of undeclared identifier 'INT_MAX'"
compilation error.
|
|/ /
| |
| |
| | |
Reland commit f2885f6 that has been trampled by commit d64a2d99.
|
| |
| |
| |
| |
| | |
StringSpaceUsedExcludingSelf has been part of the lite library since
b913cbd.
|
|\ \
| | |
| | | |
MessageOptions should handle both proto2 and google.protobuf package names.
|
| | |
| | |
| | |
| | |
| | |
| | | |
MessageOptions.
This is done so that the same library can be used irrespective of whether MessageOptions belong to package name 'proto2' or 'google.protobuf'
|
|\ \ \
| |/ /
|/| | |
Fixes deprecation warnings/errors on Xcode
|
| | | |
|
| | |
| | |
| | |
| | | |
mac version to that if atomic is enabled
|
|/ / |
|
| |
| |
| |
| |
| |
| | |
The size parameter is only used in cases where the compiler supports
sized delete, so when that's not available we need to specifically cast
it to void to prevent a warning.
|
|\ \
| | |
| | | |
[arm/gcc] Don't rely on KUSER_HELPERS feature for atomics
|
| | |
| | |
| | |
| | |
| | |
| | | |
ARM specific CONFIG_KUSER_HELPERS feature can be disabled in Linux kernel,
and in this case, we shouldn't crash. Use gcc built-in functions instead
of arm specific code if they are available.
|
|\ \ \
| | | |
| | | | |
generic atomicops: Use strong compare_exchange
|
| |/ /
| | |
| | |
| | |
| | | |
Weak compare-and-exchange are allowed to fail spuriously, so we have
to use the strong variation here.
|
|/ /
| |
| | |
When running >bazel test :protobuf_test a few compiler warnings came up. They were centered around the usage of "int" as the loop counter where the value should have been a size_t.
|
| | |
|
| | |
|
| | |
|
|\ \
| |/
|/| |
|
| |\
| | |
| | | |
Fix MSVC build when HAVE_LONG_LONG is defined.
|
| | | |
|
| |\ \
| | | |
| | | | |
Fixed references to foreign nested messages with CommonJS-style imports
|
| | |/
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
A bug was causing generated JSPB code with CommonJS-style imports to
refer incorrectly to nested messages from other .proto files. The
generated code would have things like "test_pb.InnerMessage" instead of
"test_pb.OuterMessage.InnerMessage". This commit fixes the problem by
correctly taking into account any message nesting.
|
| |/
| |
| |
| |
| |
| |
| |
| | |
There seem to already be .proto files out there that have conflicting
enum names, which will not be able to build successfully for some
languages (like C#). To prevent this problem from spreading, let's make
it an error for proto3 but just issue a warning for proto2. This fixes
issue #2179.
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
Change-Id: I6a5078b6bcdf4637e11c1cb9da1f74298e6fc26e
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
(#2146)
Currently deserialization of a non-packed binary repeated field is quadratic in
the number of elements, because each time we parse a new element we copy over
all elements we have parsed so far. This CL fixes the performance problem by
having the generated deserialization code just call addX() instead of using
getX() and setX().
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
There seem to already be .proto files out there that have conflicting
enum names, which will not be able to build successfully for some
languages (like C#). To prevent this problem from spreading, let's make
it an error for proto3 but just issue a warning for proto2. This fixes
issue #2179.
|
| |
| |
| |
| |
| |
| |
| |
| | |
A bug was causing generated JSPB code with CommonJS-style imports to
refer incorrectly to nested messages from other .proto files. The
generated code would have things like "test_pb.InnerMessage" instead of
"test_pb.OuterMessage.InnerMessage". This commit fixes the problem by
correctly taking into account any message nesting.
|
| | |
|
| | |
|