From: silas poulson <silas8642@hotmail.co.uk>
To: Paul Ruizendaal via TUHS <tuhs@minnie.tuhs.org>
Subject: [TUHS] Compilation "vs" byte-code interpretation, was Re: Looking back to 1981 - what pascal was popular on what unix?
Date: Sun, 30 Jan 2022 20:09:41 +0000 [thread overview]
Message-ID: <A6545CF1-D7FD-444E-B060-3E07DBC92C2F@hotmail.co.uk> (raw)
In-Reply-To: <A84C7761-A80D-4F8D-B541-2C7F7E5B5E39@hotmail.co.uk>
[-- Attachment #1: Type: text/plain, Size: 955 bytes --]
Resending this as realised accidentally replied off list
Silas
On 30 Jan 2022, at 18:39, silas poulson <silas8642@hotmail.co.uk<mailto:silas8642@hotmail.co.uk>> wrote:
On 30 Jan 2022, at 18:07, Dan Stromberg <drsalists@gmail.com<mailto:drsalists@gmail.com>> wrote:
And is Java? They both have a byte code interpreter.
My understanding is Java is both a compiled and interpreted language -
with javac compiling java code to byte code and then JVM interpreting
and executing the byte code.
And then there's the CPython implementation of Python. <snip>
Granted, it has an implicit, cached compilation step, but is it less compiled for that?
I would so no - in my mind compiling analyses the entire source and
then translates it whilst interpreters only explore a single line or
expression. Simply because the compilation happens only Just In Time,
doesn’t make it any less of a compilation step.
Hope that helps,
Silas
[-- Attachment #2: Type: text/html, Size: 1929 bytes --]
next parent reply other threads:[~2022-01-30 20:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A84C7761-A80D-4F8D-B541-2C7F7E5B5E39@hotmail.co.uk>
2022-01-30 20:09 ` silas poulson [this message]
2022-01-28 23:07 [TUHS] " Will Senn
2022-01-29 19:59 ` Clem Cole
2022-01-30 16:57 ` David Barto
2022-01-30 18:07 ` [TUHS] Compilation "vs" byte-code interpretation, was " Dan Stromberg
2022-01-30 20:09 ` David Barto
2022-01-31 7:59 ` WEB
2022-01-30 22:51 ` Dan Cross
2022-01-30 23:57 ` Dan Stromberg
2022-01-31 0:23 ` Nemo Nusquam
2022-01-31 0:45 ` Steve Nickolas
2022-01-31 17:16 ` Paul Winalski
2022-01-31 20:00 ` Erik E. Fair
2022-01-31 22:45 ` Steve Nickolas
2022-02-02 4:53 ` Adam Thornton
2022-01-31 1:41 ` Phil Budne
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=A6545CF1-D7FD-444E-B060-3E07DBC92C2F@hotmail.co.uk \
--to=silas8642@hotmail.co.uk \
--cc=tuhs@minnie.tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).