aboutsummaryrefslogtreecommitdiffhomepage
path: root/src/google/protobuf/compiler/java/java_file.cc
Commit message (Collapse)AuthorAge
* Merge pull request #4504 from xfxyjwf/liteGravatar Feng Xiao2018-04-18
|\ | | | | Cleanup + documentation for Java Lite runtime.
* | Fixed a Visual Studio 2017 build error. (#4488)Gravatar Ronny Krüger2018-04-16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The current 15.6.x versions of Visual Studio 2017 contain a bug that prevent them from compiling the following construct under certain conditions: std::unique_ptr<std::unique_ptr<Foo> []> foos; This will fail to compile if Foo is an abstract class. To work-around the problem the whole construct was change into: std::vector<std::unique_ptr<Foo>> foos; This not only fixes the compiler error but is also more readable than previous version.
| * Cleanup + documentation for Java Lite runtime.Gravatar Feng Xiao2018-04-12
|/
* Integrated internal changes from GoogleGravatar Adam Cozzette2018-03-13
|
* Add @Deprecated annotation support for proto file.Gravatar Jisi Liu2017-08-31
|
* Merge from Google internal for 3.4 releaseGravatar Jisi Liu2017-07-18
|
* Down-integrate from google3.Gravatar Feng Xiao2017-03-29
|
* const FieldDescriptorCompareGravatar Ross Wang2017-02-17
| | | | | | | Clang now validates that <set> comparators must have a const operator(): https://reviews.llvm.org/rL291969 Discussion: https://groups.google.com/d/msg/protobuf/9W6zFIHaJ-4/9RrfwelpEQAJ
* Integrated internal changes from GoogleGravatar Adam Cozzette2016-11-17
|
* Integrate internal changesGravatar Bo Yang2016-10-10
|
* Integrate from internal code base.Gravatar Feng Xiao2016-07-13
|
* Integrated internal changes from GoogleGravatar Adam Cozzette2016-06-29
| | | | This includes all internal changes from around May 20 to now.
* Integrate google internal changes.Gravatar Jisi Liu2016-03-30
|
* Down-integrate from internal code base.Gravatar Feng Xiao2015-12-11
|
* down-integrate internal changesGravatar Bo Yang2015-05-21
|
* CR feedback: spacing, document return valuesGravatar Daniel Martin2015-04-08
|
* Fix java compilation issues when processing large .proto filesGravatar Daniel Martin2014-11-25
| | | | | | | | | | Fix issues 579 and 501 on the code.google.com issues list. Specifically, large .proto files lead to too much static code, leading to a compilation error from javac: "code too large". This divides the code used in static initialization into multiple methods to avoid that error. Also, this incorporates the fix in issue 501 on the code.google.com issues list to call registry.add only once per extension.
* Down-integrate from internal code base (C++ maps support).Gravatar Feng Xiao2014-11-14
|
* Down-integrate from internal code base.Gravatar Feng Xiao2014-11-10
|
* Replace links to code.google.com/protobuf with ↵Gravatar Feng Xiao2014-10-01
| | | | developers.google.com/protocol-buffers
* Change java descriptor back to privateGravatar jieluo@google.com2014-08-07
|
* change java compiler to only produce one java fileGravatar jieluo@google.com2014-08-07
|
* down integrate to svnGravatar jieluo@google.com2014-07-18
|
* Down-integrate from internal branchGravatar xiaofeng@google.com2012-09-22
|
* Submit recent changes from internal branch. See CHANGES.txt for more details.Gravatar liujisi@google.com2010-11-02
|
* Massive roll-up of changes. See CHANGES.txt.Gravatar kenton@google.com2009-12-18
|
* Gigantic descriptors shouldn't overflow the Java string literal size limit.Gravatar kenton@google.com2009-08-07
|
* Submit recent changes from internal branch, including "lite mode" forGravatar kenton@google.com2009-07-29
| | | | | C++ and Java. See CHANGES.txt for more details.
* Integrate changes from internal Google-internal branch.Gravatar kenton@google.com2008-09-24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | General * License changed from Apache 2.0 to New BSD. * It is now possible to define custom "options", which are basically annotations which may be placed on definitions in a .proto file. For example, you might define a field option called "foo" like so: import "google/protobuf/descriptor.proto" extend google.protobuf.FieldOptions { optional string foo = 12345; } Then you annotate a field using the "foo" option: message MyMessage { optional int32 some_field = 1 [(foo) = "bar"] } The value of this option is then visible via the message's Descriptor: const FieldDescriptor* field = MyMessage::descriptor()->FindFieldByName("some_field"); assert(field->options().GetExtension(foo) == "bar"); This feature has been implemented and tested in C++ and Java. Other languages may or may not need to do extra work to support custom options, depending on how they construct descriptors. C++ * Fixed some GCC warnings that only occur when using -pedantic. * Improved static initialization code, making ordering more predictable among other things. * TextFormat will no longer accept messages which contain multiple instances of a singular field. Previously, the latter instance would overwrite the former. * Now works on systems that don't have hash_map. Python * Strings now use the "unicode" type rather than the "str" type. String fields may still be assigned ASCII "str" values; they will automatically be converted. * Adding a property to an object representing a repeated field now raises an exception. For example: # No longer works (and never should have). message.some_repeated_field.foo = 1
* Initial checkin.Gravatar temporal2008-07-10
generated by cgit v1.2.3 (git 2.39.1) at 2024-05-20 19:14:22 +0000