Changes between Version 14 and Version 15 of LoritoRoadmap

Timestamp:

06/03/10 23:38:26 (12 years ago)

Author:

cotto

Comment:

put primary design questions in the approximate order they'll need to be answered

LoritoRoadmap

@@ -12 +12 @@
  * Define Lorito ops and semantics.
    * Primary issues (should be decided before serious prototyping begins):
-     * purpose (why does it exist, what role does it fill, what is it, what is it not)
-     * how to deal with native types and call C-level functions (ffi)
+     * purpose (why does it exist, what role does it fill, what is it, what is it not, etc)
+     * security model
+     * concurrency (will we support multiple models or a single one, and can an HLL use another model?)
+     * [http://lists.parrot.org/pipermail/parrot-dev/2010-March/003951.html proper balance] between op simplicity and ease of bytecode validation
+     * how to deal with platform-native types and call C-level functions (ffi)
      * arg format (fixed three-arg format, variable, other)
-     * classes of ops, specific op set
-     * security model
-     * concurrency
-     * [http://lists.parrot.org/pipermail/parrot-dev/2010-March/003951.html proper balance] between op simplicity and ease of bytecode validation
-     * interaction with PMCs (i.e. what does the Lorito for RPA look like?)
+     * classes of ops, specific op set (with the expectation that once settled, this will change seldom or never)
      * registers (will PMCs have distinct registers or be represented simply as pointers)
+     * 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?)
    * Secondary issues (can be decided as implementations progress):
      * binary format (Will PBC eventually contain Lorito ops?  If not, how will composed ops be represented?)