- 02 Apr, 2018 1 commit
-
-
Thomas Van Lenten authored
To ensure all headers aren't dependent on other things being imported before/after them, make a source that just imports each header and add it to the unittesting target, that way we ensure it can be included on its own with ordering issues. Also do this testing with a few generated headers that aren't part of the library to help ensure the different generated imports needed are complete.
-
- 29 Jan, 2016 1 commit
-
-
Jisi Liu authored
Java files are moved to un-do the hack in the prevous commit, which moved the java files to the original position for integration.
-
- 28 Jan, 2016 1 commit
-
-
Jisi Liu authored
Moving the files to their original location, so that opensource changes can be picked during the internal merge. Those files will be moved into the correct location after merging with internal code. Note: do NOT merge this into master without the other internal down-integration commit.
-
- 13 Jan, 2016 1 commit
-
-
nmittler authored
protobuf/java will become a parent pom that will contain two modules: core - contains all of the code for the protobuf-java artifact util - contains all of the code for the protobuf-java-util artifact Also cleaned up various Maven warnings.
-
- 11 Nov, 2014 1 commit
-
-
Feng Xiao authored
-
- 01 Oct, 2014 1 commit
-
-
Feng Xiao authored
-
- 18 Jul, 2014 1 commit
-
-
jieluo@google.com authored
-
- 02 Nov, 2010 1 commit
-
-
liujisi@google.com authored
-
- 29 Jul, 2009 1 commit
-
-
kenton@google.com authored
C++ and Java. See CHANGES.txt for more details.
-
- 22 Oct, 2008 1 commit
-
-
Jon Skeet authored
-
- 24 Sep, 2008 1 commit
-
-
kenton@google.com authored
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
-
- 14 Aug, 2008 1 commit
-
-
Jon Skeet authored
committer: Jon Skeet <skeet@pobox.com>
-
- 10 Jul, 2008 1 commit
-
-
temporal authored
-