Sujet : Re: Command Languages Versus Programming Languages
De : cross (at) *nospam* spitfire.i.gajendra.net (Dan Cross)
Groupes : comp.unix.shell comp.unix.programmer comp.lang.miscDate : 11. Oct 2024, 16:45:01
Autres entêtes
Organisation : PANIX Public Access Internet and UNIX, NYC
Message-ID : <vebh5t$mnh$1@reader1.panix.com>
References : 1 2 3 4
User-Agent : trn 4.0-test77 (Sep 1, 2010)
In article <
vebffc$3n6jv$1@dont-email.me>, <
Muttley@DastartdlyHQ.org> wrote:
On Fri, 11 Oct 2024 15:47:06 +0100
Rainer Weikusat <rweikusat@talktalk.net> boring babbled:
Bart <bc@freeuk.com> writes:
Interpreter? Perl has some kind of compiler in it, right?
>
The Perl compiler turns Perl source code into a set of (that's a
>
Does it produce a standalone binary as output? No, so its an intepreter
not a compiler. However unlike the python interpreter its non interactive
making it an even less attractive option these days.
That's a bad distinction. There have been "Load and Go"
compilers in the past that have compiled and linked a program
directly into memory and executed it immediately after
compilation. As I recall, the Waterloo FORTRAN compilers on the
IBM mainframe did, or could do, more or less this.
Saving to some sort of object image is not a necessary function
of a compiler.
- Dan C.