Re: What would a compiler interpreter that executes machine code be called?

I think that term "Compile and go" is strongly associated with the
70's student batch compilers, like Watfor (for those of us that
remember.) While the dominant model for current "native code"
compilers are still essentially "compile, link and go", interpreter
systems such as Perl and Python are not at all like the old batch
"compile and go" systems, in that they are embeddable, dynamically
extensible, and their type meta-systems are available at run time.
The Watfor and like systems were essentially sub-hosted batch
operating system environments. I don't just want a term to express
"this is a a compiler that doesn't use or need a linker and loader".


The kind of system I want to refer to or associate with this term
would be, say the various Oberon or Black Box Component Pascal
systems. (Not Java VMs with just-in-time compiling, as in that kind of
framework, compilation of source code is a separate step to executing
the byte code with the Java VM.)


I am looking for a compact term that expresses the noun form of a
verb, as in "the interpreter interpreted my program". I don't think
that "the compile'n-goer compiled'n-went my program" makes the
grade. As far as I can tell, a new term is needed, and I am interested
in creative suggestions.


- Parzival


Parzival <parz@RemoveThisSpamBucket.home.com> wrote in message
> I was doing some writing, and I wanted to discuss a compiler that
> compiled to native machine code in memory, and then executed that
> code, and I am lacking a term.
....
> [I'd suggest "compile and go", that's what we always used to call it. -John]

Return to the comp.compilers page.
Search the comp.compilers archives again.