Author Commit Message Date
Work around GCC 4.3.0 x86_64 compiler bug (seen on Fedora 9). Details: For each message type, protoc generates an array of byte offsets of each of the fields within the message class. These offsets are later used by the reflection implementation. Prior to this revision, the offset arrays were allocated as global variables. Since they were just arrays of ints, they should have been initialized at compile time. Unfortunately, GCC 4.3.0 incorrectly decides…
Update MSVC installation instructions for static linking change.
Avoid an "unused parameter" warning when using high warning levels.
Update version number to 2.0.3-SNAPSHOT.
Make Python example output identical to C++ and Java by removing redundant spaces.
Set version to 2.0.2 in release branch.
Set version to 2.0.2 in release branch.
Tag release 2.0.2 (take 2).
Oops, wrong name.
Tag release 2.0.2.
* Fixed template specialization syntax that MSVC 2005 didn't like. Not sure if it was valid or not. * Moved UTF-8 coding directive to the right place in
Improvements to from Jeff Bailey.
Pass -Wall,no-obsolete to autoreconf.
Added clarification to license that generated code is owned by the owner of the input file.
Update version number in 2.0.2rc1 release branch.
Update version number in 2.0.2rc1 release branch.
Tagged release candidate 2.0.2rc1.
* Fix build on MSVC. * Switch to statically-linked libraries instead of DLLs on MSVC.
Add file missing from rev 50.
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; …
Add file that was mysteriously missing from SVN tree.
Explicitly identify superclass in initializer lists for generated message classes. This avoids a warning when using GCC's -pedantic option.
Work around absence of hash_map. Also, update version numbers to 2.0.2-SNAPSHOT.
Add @Override annotation to generated Java code where appropriate. Patch from Brian Atkinson <>.
Add code suggested by Michal Januszewski <> to ensure that Python tests run correctly even when a previous version of the library is already installed. I was unable to reproduce his problem on my machine but the fix seems harmless enough.
Tag the 2.0.1 release.
2.0.1 release.
More prep for 2.0.1: * Fix version number test so that it accepts "2.0.1rc1". * Add missing to
Add missing module to
  1. Prev
  2. Next