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.
 
 
 
 
 
 
Josh Haberman a25c50361a Added optimization note. 10 years ago
..
googlepb Sync from internal Google development. 11 years ago
linux Sync to internal Google development. 11 years ago
lua Sync from Google-internal development. 11 years ago
python Sync to internal Google development. 11 years ago
ruby Added optimization note. 10 years ago
stdc Sync from internal Google development. 11 years ago
stdc++ Sync from internal Google development. 11 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/.