protobuf

Commit Graph

Author	SHA1	Message	Date
Nobuaki Sukegawa	33bb176603	Add oneof keyword to proto.vim	10 years ago
Feng Xiao	e428862450	Replace links to code.google.com/protobuf with developers.google.com/protocol-buffers	10 years ago
liujisi@google.com	d0e03932c1	Fix issue/333. skip any escaped characters in quotes.	13 years ago
liujisi@google.com	5325de1808	Support for C-style comments in editors/proto.vim -- patch from infnty.	14 years ago
kenton@google.com	d5cf7b55a6	Some sort of emacs protobuf mode fix.	15 years ago
kenton@google.com	f4c6e4b37e	Fix protobuf-mode on XEmacs.	15 years ago
kenton@google.com	31afcd730b	Fix problems with emacs protobuf mode, I guess. See <http://www.opensubscriber.com/message/emacs-devel@gnu.org/7155093.html >. Patch from domq@google.com.	16 years ago
kenton@google.com	2cdba5baee	Add Emacs editor mode. Contributed by Alexandre Vassalotti.	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
temporal	8ccb79057e	Apply Leandro Lucarella <llucax@gmail.com>'s patches for VIM highlighting and not setting execute bit on protoc outputs.	17 years ago
temporal	40ee551715	Initial checkin.	17 years ago

11 Commits (59692c3fc080645fdc6e8d2445f04a1d65cee48c)