protobuf

Commit Graph

Author	SHA1	Message	Date
listonjesse	2ae7cf0e03	Auxillary -> Auxiliary	5 years ago
Joshua Haberman	6ed738305b	Sync from Piper @311396324 PROTOBUF_SYNC_PIPER	5 years ago
Adam Cozzette	d64a2d9941	Integrated internal changes from Google This includes all internal changes from around May 20 to now.	9 years ago
Feng Xiao	6ef984af4b	Down-integrate from internal code base.	10 years ago
Feng Xiao	e428862450	Replace links to code.google.com/protobuf with developers.google.com/protocol-buffers	10 years ago
jieluo@google.com	bde4a3254a	down integrate python opensource to svn	10 years ago
xiaofeng@google.com	b55a20fa2c	Down-integrate from internal branch	12 years ago
kenton@google.com	d37d46dfbc	Integrate recent changes from Google-internal code tree. See CHANGES.txt for details.	16 years ago
Jon Skeet	f0589506c9	Wiping slate clean to start again with new layout.	16 years ago
kenton@google.com	24bf56fb3a	Integrate changes from internal Google-internal branch. 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	16 years ago
Jon Skeet	f92c545f49	Initial commit of C# code developed before installing Git. committer: Jon Skeet <skeet@pobox.com>	17 years ago
temporal	40ee551715	Initial checkin.	17 years ago

1 Commits (0dd5fffba3600cc96b011319cf566dd501152f41)