Difference between revisions of "TypeSystems"
Jump to navigation
Jump to search
Line 36: | Line 36: | ||
|- | |- | ||
|bytes | |bytes | ||
+ | |} | ||
There are some additional types that would be nice to add: | There are some additional types that would be nice to add: | ||
+ | |||
{| border="1" cellpadding="0" | {| border="1" cellpadding="0" | ||
!width="50"|Name||Basic Types Built From | !width="50"|Name||Basic Types Built From |
Revision as of 00:11, 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 |
---|
double |
float |
int32 |
int64 |
uint32 |
uint64 |
sint32 |
sint64 |
fixed32 |
fixed64 |
sfixed32 |
sfixed64 |
bool |
string |
bytes |
There are some additional types that would be nice to add:
Name | Basic Types Built From |
---|---|
Fixed Length Arrays | bytes |
UUID | Fixed Length Array [16] |
URI | Variable Length Array of Strings |
Time | |
Duration | |
flags (enum where each enumerant can be toggled) | |
Vector3f | |
Vector2f | |
Vector3d | |
Vector2d | |
Quaternion | |
Angle (0-2pi) | |
Bounding box/sphere (NULL defined) |