-For native code ABI defines convention to ease tooling integration. +
For native code ABI defines convention to ease tooling integration. Platform/compiler C ABI is assumed, + but it should be trivially expressible in JSON-RPC as well.
- 32 bit floating point is the only numeric type.
- Procedure parameters can only use basic types, with no aggregates. Exceptions are Vec, Rect and Color types. (see /include/twn_types.h) -
- Enum types are not allowed, as they decay to integer type, identity strings are used instead. +
- Enum types are allowed, but must be converted to floats. Identity strings are preferred.
- No opaque nor pointer types allowed, use string keys if needed. Think of it as data base relations.
- Only null terminated string is allowed as a sequential type in both parameters and returns.
- Return value could be a simple aggregate that is translatable to a dictionary of primitives, without nesting. @@ -70,6 +71,8 @@
- Parameter names should not collide with keywords of any language that is targeted; if so happens, parameter alias could be added. Currently forbidden: repeat.
- Procedure can't have more than 8 parameters. +
- Decimal portions of floating points are lossy both due to rounding errors and text representation, + thus they cannot be relied to hold for equality. Integer parts of floats are good up to 2^24.