Return to the
comp.compilers page.
Search the
comp.compilers archives again.
| Related articles |
|---|
| The melting ice technology (1): compilers & interpreters bertrand@eiffel.com (1994-05-09) |
| The melting ice technology (2): levels bertrand@eiffel.com (1994-05-09) |
| Re: The melting ice technology (2): levels peter@objy.com (1994-05-12) |
| Re: The melting ice technology (2): levels mhcoffin@tolstoy.uwaterloo.ca (1994-05-13) |
| Re: The melting ice technology (2): levels papresco@undergrad.math.uwaterloo.ca (1994-05-13) |
| Re: The melting ice technology (2): levels lgm@polaris.ih.att.com (1994-05-14) |
| Re: The melting ice technology (2): levels pdlogan@ccm.jf.intel.com (1994-05-16) |
| Newsgroups: | comp.lang.eiffel,comp.compilers |
| From: | pdlogan@ccm.jf.intel.com (Patrick D. Logan) |
| Keywords: | interpreter, Eiffel, Lisp, C++ |
| Organization: | Intel / ProShare |
| References: | 94-05-019 94-05-052 |
| Date: | Mon, 16 May 1994 15:18:28 GMT |
lgm@polaris.ih.att.com (Lawrence G. Mayka) writes:
>But this all only demonstrates that the principle of offering more
>than one space/run-speed/compilation-speed tradeoff is a sound one.
Plus the technology of easily and quickly replacing a module compiled with
one set of choices by the module compiled with a different set of choices,
i.e the "melting ice" idea.
As a counter-example, Microsoft C++ can create p-code or native code. So
you can choose the space/speed most apprporiate. But they don't have a
"melting ice" capability for an interpreter-like behavior. Maybe someday?
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.