Changes between Version 11 and Version 12 of LoritoRoadmap
- Timestamp:
- 06/02/10 06:51:27 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
LoritoRoadmap
v11 v12 11 11 === Lorito Design === 12 12 * Define Lorito ops and semantics. 13 * Primary issues (should be decided before serious prototyping can begin): 13 * Primary issues (should be decided before serious prototyping begins): 14 * purpose (why does it exist, what role does it fill, what is it, what is it not) 14 15 * how to deal with native types and call C-level functions (ffi) 15 16 * arg format (fixed three-arg format, variable, other) 16 * classes of ops 17 * classes of ops, specific op set 17 18 * security model 18 19 * interaction with PMCs 19 20 * registers (will PMCs have distinct registers or be represented simply as pointers) 20 21 * Secondary issues (can be decided as implementations progress): 21 * binary format ( i.e. will PBC eventually contain Lorito)22 * binary format (Will PBC eventually contain Lorito ops? If not, how will composed ops be represented?) 22 23 * textual format 24 * backward and forward compatibility 23 25 * composition of PIR ops from Lorito ops 24 * how will bytecode be used ( i.e. local caching optimization, distributed directly, only present as an intermediate step during compilation)26 * how will bytecode be used (e.g. local caching optimization, distributed directly, only present as an intermediate step during compilation) 25 27 * minimizing bytecode bloat (if PBC will eventually become Lorito-based) 26 28 * Implement some PMCs, ops and library bindings in Lorito to demonstrate that Lorito is sufficiently powerful.