From: Dan Stromberg <email@example.com>
To: Dan Cross <firstname.lastname@example.org>
Cc: TUHS main list <email@example.com>
Subject: Re: [TUHS] Compilation "vs" byte-code interpretation, was Re: Looking back to 1981 - what pascal was popular on what unix?
Date: Sun, 30 Jan 2022 15:57:41 -0800 [thread overview]
Message-ID: <CAGGBd_qV70LY9zxRVX78wJF3VyM7paSdZSyuP7Ngb-tJBOiE3w@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1541 bytes --]
On Sun, Jan 30, 2022 at 2:52 PM Dan Cross <firstname.lastname@example.org> wrote:
> On Sun, Jan 30, 2022 at 1:08 PM Dan Stromberg <email@example.com> wrote:
>> On Sun, Jan 30, 2022 at 8:58 AM David Barto <firstname.lastname@example.org> wrote:
>>> Yes, the UCSD P-code interpreter was ported to 4.1 BSD on the VAX and it
>>> ran natively there. I used it on sdcsvax in my senior year (1980).
>> Wasn't Java referred to as "compiled" even back before the JIT compiler
>> was added?
> And then there's the CPython implementation of Python. It too uses a byte
>> code interpreter, but it's commonly referred to as "interpreted". But is
>> it really? Granted, it has an implicit, cached compilation step, but is it
>> less compiled for that?
> I think that "interpreted" in this context means the load-and-go nature of
> the system and the transience of the bytecode: the text is internally
> compiled and then executed, but these steps are often linked and, while one
> can coax the Python "interpreter" to emit .pyc and/or .pyo files, usually
> one does not: the compiled bytecodes are lost as soon as the program is
> done executing.
An interesting response.
I'll point out though, being a little picky, that python's "import"
statement will look for a .py, compile it, and write the byte code as a
.pyc - automatically. Then on subsequent invocations of the program(s)
using this module it will compare timestamps on the .py and .pyc and if the
.pyc is more recent than the .py, the compilation step will be skipped.
[-- Attachment #2: Type: text/html, Size: 2950 bytes --]
next prev parent reply other threads:[~2022-01-30 23:58 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 23:07 [TUHS] " Will Senn
2022-01-28 23:18 ` Dan Cross
2022-01-28 23:31 ` Will Senn
2022-01-29 0:03 ` Rob Pike
2022-01-29 0:40 ` Will Senn
2022-01-29 19:05 ` John Cowan
2022-01-29 19:36 ` arnold
2022-01-29 19:59 ` Clem Cole
2022-01-29 20:02 ` Jon Steinhart
2022-01-29 20:13 ` Bakul Shah
2022-01-29 20:30 ` Clem Cole
2022-01-29 20:34 ` Larry McVoy
2022-01-29 21:03 ` Al Kossow
2022-01-29 21:38 ` Larry McVoy
2022-01-29 22:06 ` Bakul Shah
2022-01-29 22:48 ` GREEN
2022-01-30 3:27 ` Larry McVoy
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 [this message]
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
2022-02-07 3:04 ` [TUHS] " Rob Gingell
[not found] <A84C7761-A80D-4F8D-B541-2C7F7E5B5E39@hotmail.co.uk>
2022-01-30 20:09 ` [TUHS] Compilation "vs" byte-code interpretation, was " silas poulson
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).