Editor's Notes
- #3: Description of purpose:What exact problem, issue, or question does this research address and why does it matter?What limitations or failings of current understanding, knowledge, methods, or technologies does this research resolve?
- #5: Description of purpose:What exact problem, issue, or question does this research address and why does it matter?What limitations or failings of current understanding, knowledge, methods, or technologies does this research resolve?
- #7: Relevant concepts for a VMEnable high-level language constructsEnable performance optimizationsNeed to be fundamentalAdditive extensions do not solve the problem
- #10: Ok, there are languages which support localityWould be a pity to not preserve that knowledge for runtime optimizations
- #12: Actor solutions on the JVM: either inefficient (copying, serializing) or complex with type systemsEffort has to be duplicated for every new actor-like languageEncapsulation: dynamic constrains on mutability (often depending on owner/locality)
- #14: Consequences: memory model -> is a field for a lot theoretic research, and has a lot low-level performance implications, our approach will be driven by the experiments, thus, it is not the main focus, but needs some attention for build/designing VMs
- #15: Technical approach – What experiments, prototypes, or studies are being performed done to achieve the stated goal? How will they be measured, evaluated and validated?
- #16: Validate their usefulness as fundamental conceptsDesign useful incarnation for a virtual machineInvestigate interaction of different models
- #22: http://blogs.msdn.com/b/codeanalysis/archive/2007/11/20/maintainability-index-range-and-meaning.aspx