aboutsummaryrefslogtreecommitdiffhomepage
path: root/editors/proto.vim
Commit message (Collapse)AuthorAge
* down-integrate internal changesGravatar Bo Yang2015-05-21
|
* Add oneof keyword to proto.vimGravatar Nobuaki Sukegawa2014-11-27
|
* Replace links to code.google.com/protobuf with ↵Gravatar Feng Xiao2014-10-01
| | | | developers.google.com/protocol-buffers
* Fix issue/333. skip any escaped characters in quotes.Gravatar liujisi@google.com2012-07-13
|
* Support for C-style comments in editors/proto.vim -- patch from infnty.Gravatar liujisi@google.com2011-07-05
|
* 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
* Apply Leandro Lucarella <llucax@gmail.com>'s patches for VIM highlightingGravatar temporal2008-07-31
| | | | | and not setting execute bit on protoc outputs.
* Initial checkin.Gravatar temporal2008-07-10