- 08 Dec, 2016 1 commit
-
-
Thomas Van Lenten authored
- Check the parent file options for deprecation when deciding to tag Messages and Enums as deprecated. - Within the generated source push/pop the warning for implementing deprecated things around a deprecated class implementation. - Annotate the methods generated for extension fields as deprecated. - Add a testing .proto file that covers deprecated fields, messages, enums, enum values and compile it into the unittests to confirm things compile cleanly. - Add a testing .proto file that uses the file level option to make everything deprecated and compile it into the unittests to confirm things compile cleanly.
-
- 01 Sep, 2016 1 commit
-
-
Thomas Van Lenten authored
At generation time, walk the file's dependencies to see what really contains extensions so we can generate more minimal code that only links together the roots that provided extensions. Gets a bunch of otherwise noop code out of the call flow when the roots are +initialized.
-
- 26 Jun, 2015 1 commit
-
-
Jon Skeet authored
- Remove some old proto2-based C#-only messages - Remove the "build" directory which only contained out-of-date files - Remove the csharp_namespace option from proto2 messages - Change "Google.ProtocolBuffers" to "Google.Protobuf" in other messages
-
- 06 May, 2015 1 commit
-
-
Jon Skeet authored
-
- 11 Nov, 2014 1 commit
-
-
Feng Xiao authored
-
- 01 Oct, 2014 1 commit
-
-
Feng Xiao 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
-