Chiebot-Mirror
/
protobuf
mirror of https://github.com/protocolbuffers/protobuf.git
8
0
Fork 0
Code Issues Projects Releases Wiki Activity
Protocol Buffers - Google's data interchange format (grpc依赖) https://developers.google.com/protocol-buffers/
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
685 Commits
201 Branches
346 Tags
254 MiB
 
 
 
 
 
 
Tag: Branch: Tree: 3122535726
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '3122535726'
${ noResults }
protobuf/upb/bindings/googlepb
Josh Haberman e977c0af03
Fixed more bugs surfaced by Travis. 		8 years ago
..
README Sync to internal Google development. 11 years ago
bridge.cc Added UPB_ASSERT() that helps avoid unused var warnings. 9 years ago
bridge.h Added UPB_ASSERT() that helps avoid unused var warnings. 9 years ago
proto1.cc Added UPB_ASSERT() that helps avoid unused var warnings. 9 years ago
proto1.int.h Brought into compliance with Google open-source policies. 10 years ago
proto2.cc Fixed more bugs surfaced by Travis. 8 years ago
proto2.int.h Brought into compliance with Google open-source policies. 10 years ago

README 

This directory contains code to interoperate with Google's official
Protocol Buffers release.  Since it doesn't really have a name
besides "protobuf," calling this directory "googlepb" seems like the
least confusing option, since it lives in the google::protobuf
namespace.

We support writing into protobuf's generated classes (and hopefully
reading too, before long).  We support both the open source protobuf
release and the Google-internal version (which is mostly the same
code, just in a different namespace). A single compile of upb can
support both (there are no conflicts thanks to function overloading).

The internal version supports some features that are not supported in
the open-source release.  Also, the internal version includes the
legacy "proto1" classes which we must support; thankfully this is
mostly relegated to its own separate file.

Our functionality requires the full google::protobuf::Message
interface; we rely on reflection so we know what fields to read/write
and where to put them, so we can't support MessageLite.