Path: csiph.com!usenet.pasdenom.info!news.albasani.net!rt.uk.eu.org!newsfeed.xs4all.nl!newsfeed3.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail
MIME-Version: 1.0
In-Reply-To: <51be19f1$0$29966$c3e8da3$5496439d@news.astraweb.com>
References: <2bc90d3b-09c2-4315-9357-ff7f039465e0@googlegroups.com> <kpckqb$28k2$3@news.ntua.gr> <51ba6e92$0$29997$c3e8da3$5496439d@news.astraweb.com> <kpeio7$p37$7@news.ntua.gr> <qot1u85gkpq.fsf@ruuvi.it.helsinki.fi> <kpel04$spl$2@news.ntua.gr> <qotobb9f3oy.fsf@ruuvi.it.helsinki.fi> <kpeomq$spl$6@news.ntua.gr> <qotmwqsq31b.fsf@ruuvi.it.helsinki.fi> <kpf4jc$spl$15@news.ntua.gr> <51bb454c$0$29997$c3e8da3$5496439d@news.astraweb.com> <kpfhv1$4rq$2@news.ntua.gr> <bfudnQuhb7jHZibMnZ2dnUVZ_t-dnZ2d@giganews.com> <kph978$29li$6@news.ntua.gr> <mailman.3368.1371290048.3114.python-list@python.org> <kphou8$slt$1@news.ntua.gr> <mailman.3382.1371311603.3114.python-list@python.org> <kpi45d$n5$3@news.ntua.gr> <kpjm6h$4rb$1@dont-email.me> <kpjrng$hmp$1@news.ntua.gr> <kpk04c$4rb$6@dont-email.me> <kpk295$hmp$5@news.ntua.gr> <kpk5bj$ifk$1@dont-email.me> <51bdaa78$0$29966$c3e8da3$5496439d@news.astraweb.com> <mailman.3453.1371411127.3114.python-list@python.org> <51be19f1$0$29966$c3e8da3$5496439d@news.astraweb.com>
Date: Mon, 17 Jun 2013 08:26:17 +1000
Subject: Re: Compiling vs interpreting [was Re: A certainl part of an if() structure never gets executed.]
From: Chris Angelico <rosuav@gmail.com>
To: python-list@python.org
Content-Type: text/plain; charset=ISO-8859-1
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.3463.1371421585.3114.python-list@python.org>
Lines: 47
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:48484

On Mon, Jun 17, 2013 at 6:02 AM, Steven D'Aprano
<steve+comp.lang.python@pearwood.info> wrote:
> On Sun, 16 Jun 2013 12:31:59 -0700, Mark Janssen wrote:
>>> The line between compilers
>>> and interpreters is quite fuzzy.
>>
>> It shouldn't be.
>
> Of course it should be, because that reflects reality.

It's fuzzy AND it seldom even matters. Compare these three text strings:

"""'aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa'""""

"""'a'*64"""

"""\37\213\b\b*8\276Q\0\3test\0KL\244\f\0\0Ue\264\211@\0\0\0"""

"""\x78\xda\x4b\x4c\xa4\x0c\0\0\x14\x8d\x18\x41"""

Which of these is an interpreted program? I would say: All of them.
And they all produce the same output, a series of 64 copies of the
letter a. The third one is interpreted by gzip(1) and will create a
file called 'test', the fourth is a raw gzip/zlib stream and so is
interpreted by (eg) the Python zlib.decompress() function. They're all
languages, of a sort. Are they interpreted/compiled versions of that
message? Kinda. If you prepend a sfx header to them, do they become
compiled and not interpreted? Doubtful. I don't think you could say
that this ceases to be interpreted:

import zlib
print(zlib.decompress(
"""\x78\xda\x4b\x4c\xa4\x0c\0\0\x14\x8d\x18\x41"""
))

Even if you manually imported the code for zlib.decompress, in a way
that makes it impossible for your cut-down program to actually
compress data (which then breaks the principle quoted from
"Programming in Lua"), it's still fairly clearly being
interpreted/parsed the exact same way.

So it really doesn't matter (so it really doesn't matter (so it really
doesn't matter)). [1]

ChrisA

[1] http://math.boisestate.edu/gas/ruddigore/web_opera/rudd24.html