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 | ||
| − | + | {| border="1" cellpadding="2" | |
| − | + | !width="50"|Name | |
| − | + | !width="225"|Effect | |
| − | + | !width="225"|Games Found In | |
| − | + | |double | |
| − | + | |float | |
| − | + | |int32 | |
| − | + | |int64 | |
| − | + | |uint32 | |
| − | + | |uint64 | |
| − | + | |sint32 | |
| − | + | |sint64 | |
| − | + | |fixed32 | |
| − | + | |fixed64 | |
| − | + | |sfixed32 | |
| − | + | |sfixed64 | |
| + | |bool | ||
| + | |string | ||
| + | |bytes | ||
| + | } | ||
Revision as of 00:00, 14 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
| Name | Effect | Games Found In | double | float | int32 | int64 | uint32 | uint64 | sint32 | sint64 | fixed32 | fixed64 | sfixed32 | sfixed64 | bool | string | bytes
} |
|---|