Difference between revisions of "TypeSystems"
Jump to navigation
Jump to search
| Line 4: | Line 4: | ||
This gives us the following types | This gives us the following types | ||
| − | |double | + | |
| + | {|double | ||
|float | |float | ||
|int32 | |int32 | ||
| − | int64 | + | |int64 |
| − | uint32 | + | |uint32 |
| − | uint64 | + | |uint64 |
| − | sint32 | + | |sint32 |
| − | sint64 | + | |sint64 |
| − | fixed32 | + | |fixed32 |
| − | fixed64 | + | |fixed64 |
| − | sfixed32 | + | |sfixed32 |
| − | sfixed64 | + | |sfixed64 |
| − | bool | + | |bool |
| − | string | + | |string |
| − | bytes | + | |bytes |
| + | } | ||
Revision as of 23:58, 13 February 2009
We want the type system to be serialization agnostic so we can support different backends.
Our current implementation ideas revolve around starting from the serialization format specified in protocol buffers. This gives us the following types
| float | int32 | int64 | uint32 | uint64 | sint32 | sint64 | fixed32 | fixed64 | sfixed32 | sfixed64 | bool | string | bytes
} |