Changes between Version 5 and Version 6 of LoritoDesignQuestions
- Timestamp:
- 07/22/10 00:53:35 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
LoritoDesignQuestions
v5 v6 33 33 === Will Parrot's calling conventions remain the same after Lorito? === 34 34 35 PIR that works with Parrot now is expected to run without modification on a Lorito-based Parrot. This includes calling conventions. 36 35 37 === Will Lorito allow direct memory access/pointer arithmetic? === 36 38 37 39 === Will Lorito allow manual memory allocation/deallocation? === 40 41 Lorito will allow manual memory management through the same interface used to access other C-level functions. 38 42 39 43 === Will Lorito have a stack? === … … 45 49 === Will Lorito have a object model built-in? === 46 50 51 No. The object model will be implemented on top of Lorito. 52 47 53 === Will Lorito still have the same core object model as Parrot? === 54 55 Lorito will exist below the level of Parrot's object model. 48 56 49 57 === Will Lorito have a single op that does method dispatch at the lowest level or it will be simulated using a series of ops? === 50 58 51 MMD will be implemented in terms of Lorito ops.59 MMD will be implemented op top of Lorito. 52 60 53 61 === Will Lorito have some declarative syntax at the lowest level for creating classes/types? === … … 67 75 === Will objects have a static vtable in addition to method dispatch? === 68 76 77 VTABLE 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 69 79 === How should method dispatch work? === 70 80 … … 73 83 === Should method dispatch use strings or [http://en.wikipedia.org/wiki/Symbol_(Lisp) symbols]? === 74 84 75 At this point symbols are likely but this design decision hasn't been discussed yet. 85 Symbols 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? ===
