Difference between revisions of "ProtocolBuffer"
From Makers Local 256
(→Todo: add implementation comments for extensions) |
m (→Todo: add more things todo....) |
||
| Line 17: | Line 17: | ||
** PBMessage structures need two integer fields for extension ranges | ** PBMessage structures need two integer fields for extension ranges | ||
** Nested extensions modify the variable name, but the effect is still global | ** Nested extensions modify the variable name, but the effect is still global | ||
| + | * support field numbers over 15 (not specified in the encoding explanation on the website) | ||
* proper option support | * proper option support | ||
| + | * support groups (unlikely, since they are deprecated) | ||
* support services (this may not happen at all) | * support services (this may not happen at all) | ||
[[Category:Software]] | [[Category:Software]] | ||
Revision as of 11:46, 27 July 2009
|
Creator: |
Overview
ProtocolBuffer is a D library encompassing the basic tools required to compile .proto definition files into code and additional functions that are used by the resulting source file. The backend library is separated from the definition compiler for now, but those may merge in the future.
Options
At the moment, only a handful of options are supported and all others will be ignored. Options are not currently accessible at runtime. Supported options are packed, deprecated, and default.
Todo
- support extensions (this is going to suck than I thought)
- Need to figure out and tree all pbroots before writing anything
- PBMessage and PBRoot structures need a new PBChild[] for extensions
- PBMessage structures need two integer fields for extension ranges
- Nested extensions modify the variable name, but the effect is still global
- support field numbers over 15 (not specified in the encoding explanation on the website)
- proper option support
- support groups (unlikely, since they are deprecated)
- support services (this may not happen at all)
