This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |
| fifty_questions_for_a_prospective_language_designer [2007-07-10 18:19] – 71.60.251.17 | fifty_questions_for_a_prospective_language_designer [2007-07-10 18:21] (current) – 71.60.251.17 |
|---|
| | |
| |
| |
| **hugely** simplified FFI issues.) Good integration with native code probably means that you will end up using a conservative collector, and that will effect the semantics of "finalization" (if you have it). | **hugely** simplified FFI issues.) Good integration with native code probably means that you will end up using a conservative collector, and that will effect the semantics of "finalization" (if you have it). |
| |
| Do you want to be able to return multiple values? How about &rest arguments? These affect function call/return, tail-call elimination, and stack vs. heap allocation optimizations. | Do you want to be able to return multiple values? How about &rest arguments? These affect function call/return, tail-call elimination, and stack vs. heap allocation optimizations. |
| |
| What's your order of evaluation in expressions? This affects what sort of optimizations can be safely done. | What's your order of evaluation in expressions? This affects what sort of optimizations can be safely done. |
71.60.251.17