Changes between Version 5 and Version 6 of LoritoDesignQuestions

Show
Ignore:
Timestamp:
07/22/10 00:53:35 (4 years ago)
Author:
cotto
Comment:

answer a few more questions

Legend:

Unmodified
Added
Removed
Modified
  • LoritoDesignQuestions

    v5 v6  
    3333=== Will Parrot's calling conventions remain the same after Lorito? === 
    3434 
     35PIR that works with Parrot now is expected to run without modification on a Lorito-based Parrot.  This includes calling conventions. 
     36 
    3537=== Will Lorito allow direct memory access/pointer arithmetic? === 
    3638 
    3739=== Will Lorito allow manual memory allocation/deallocation? === 
     40 
     41Lorito will allow manual memory management through the same interface used to access other C-level functions. 
    3842 
    3943=== Will Lorito have a stack? === 
     
    4549=== Will Lorito have a object model built-in? === 
    4650 
     51No.  The object model will be implemented on top of Lorito. 
     52 
    4753=== Will Lorito still have the same core object model as Parrot? === 
     54 
     55Lorito will exist below the level of Parrot's object model.   
    4856 
    4957=== Will Lorito have a single op that does method dispatch at the lowest level or it will be simulated using a series of ops? === 
    5058 
    51 MMD will be implemented in terms of Lorito ops. 
     59MMD will be implemented op top of Lorito. 
    5260 
    5361=== Will Lorito have some declarative syntax at the lowest level for creating classes/types? === 
     
    6775=== Will objects have a static vtable in addition to method dispatch? === 
    6876 
     77VTABLE functions and methods will be unified post-Lorito.  The Parrot development community hasn't decided what this mechanism will be, but it is likely that the internal representation of vtable functions will change from its current form. 
     78 
    6979=== How should method dispatch work? === 
    7080 
     
    7383=== Should method dispatch use strings or [http://en.wikipedia.org/wiki/Symbol_(Lisp) symbols]? === 
    7484 
    75 At this point symbols are likely but this design decision hasn't been discussed yet. 
     85Symbols are likely but this design decision hasn't been discussed yet. 
     86 
     87=== How will Lorito support native types? === 
     88 
     89=== How will Lorito support calling C functions in existing libraries? ===