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.
619 Commits
197 Branches
346 Tags
251 MiB
 
 
 
 
 
 
Tag: Branch: Tree: 7c6a763bd8
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '7c6a763bd8'
${ noResults }
protobuf/upb/bindings
Josh Haberman 5b44720f8f
Also remove license headers from Lua. 		10 years ago
..
googlepb Brought into compliance with Google open-source policies. 10 years ago
linux Brought into compliance with Google open-source policies. 10 years ago
lua Also remove license headers from Lua. 10 years ago
python Brought into compliance with Google open-source policies. 10 years ago
ruby Brought into compliance with Google open-source policies. 10 years ago
stdc Brought into compliance with Google open-source policies. 10 years ago
stdc++ Brought into compliance with Google open-source policies. 10 years ago
README Sync to internal Google development. 11 years ago

README 

This directory contains code that interfaces upb with external C/C++
libraries.  For example:

 * upb/bindings/{stdc,stdc++}
     interfaces between upb and the standard libraries of C and C++ (like C's
     FILE/stdio, C++'s string/iostream, etc.)

 * upb/bindings/googlepb
     interfaces between upb and the "protobuf" library distributed by Google.

 * upb/bindings/lua:
     a Lua extension that exposes upb to Lua programs via the Lua C API.

 * upb/bindings/linux:
     code and build system for building upb as a Linux kernel module.

The two key characteristics that decide whether code belongs in upb/bindings/
are:

 * Does the code's public API refer to types from another library?
   If so it belongs in upb/bindings/.  But this doesn't include code that just
   happens to use another library internally, as an implementation detail.

 * Would this code be useful to someone who is not using this external library
   in some other way?  If so, the code probably doesn't belong in upb/bindings/.