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.
503 Commits
197 Branches
346 Tags
251 MiB
 
 
 
 
 
 
Tag: Branch: Tree: 7d3e2bd2c4
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '7d3e2bd2c4'
${ noResults }
protobuf/upb/google
Josh Haberman 7d3e2bd2c4
Sync with 8 months of Google-internal development. 		12 years ago
..
README Sync with 8 months of Google-internal development. 12 years ago
bridge.cc Sync with 8 months of Google-internal development. 12 years ago
bridge.h Sync with 8 months of Google-internal development. 12 years ago
cord.h Sync with 8 months of Google-internal development. 12 years ago
proto1.cc Sync with 8 months of Google-internal development. 12 years ago
proto1.h Sync with 8 months of Google-internal development. 12 years ago
proto2.cc Sync with 8 months of Google-internal development. 12 years ago
proto2.h Sync with 8 months of Google-internal development. 12 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 "google" seems like the
least confusing option.

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 of the same code.  The two
live in different namespaces, and 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.