Changes between Version 19 and Version 20 of LoritoRoadmap

Show
Ignore:
Timestamp:
10/11/10 22:01:10 (4 years ago)
Author:
cotto
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • LoritoRoadmap

    v19 v20  
    1717     * LoritoOpBalance between op simplicity and ease of bytecode validation 
    1818     * how to deal with platform-native types and call C-level functions (ffi) 
    19      * control flow, especially CPS, continuations in general, coroutines, exceptions and leave semantics 
    20      * arg format (fixed three-arg format, variable, other) 
    21      * [wiki:LoritoOps LoritoOps]: classes of ops, specific op set (with the expectation that once settled, this will change seldom or never) 
    22      * registers (will PMCs have distinct registers or be represented simply as pointers) 
    23      * interaction with PMCs (i.e. what does the Lorito for RPA look like?  What's the equivalent of STRING *s = VTABLE_get_string(INTERP, p); in Lorito?) 
     19     * [wiki:LoritoOps LoritoOps]: classes of ops, specific op set with the expectation that once settled, this will change very seldom or never 
     20     * registers (Will PMCs have distinct registers or be represented simply as pointers?  How wide will they be?) 
     21     * interaction with PMCs (i.e. what does the Lorito to implement RPA look like?  What's the equivalent of STRING *s = VTABLE_get_string(INTERP, p); in Lorito?) 
    2422   * Secondary issues (can be decided as implementations progress): 
    2523     * binary format (Will PBC eventually contain Lorito ops?  If not, how will composed ops be represented?)