Re: First Program with Python!

Path	csiph.com!aioe.org!.POSTED!not-for-mail
From	Kaz Kylheku <330-706-9395@kylheku.com>
Newsgroups	comp.programming
Subject	Re: First Program with Python!
Date	Tue, 16 Feb 2016 03:40:24 +0000 (UTC)
Organization	Aioe.org NNTP Server
Lines	22
Message-ID	<20160215192929.10@kylheku.com> (permalink)
References	<56ee81f0-8542-49e5-a177-c7794f2d48d7@googlegroups.com> <20160215083844.251@kylheku.com> <n9t1s6$825$1@dont-email.me> <n9tbhv$hp5$1@dont-email.me> <n9tk91$l97$1@dont-email.me>
NNTP-Posting-Host	OGJi3KNpFOhM58UHZwXj0w.user.gioia.aioe.org
X-Complaints-To	abuse@aioe.org
User-Agent	slrn/pre1.0.0-18 (Linux)
X-Notice	Filtered by postfilter v. 0.8.2
Xref	csiph.com comp.programming:6277

Show key headers only | View raw

On 2016-02-15, BartC <bc@freeuk.com> wrote:
> On 15/02/2016 20:16, Richard Heathfield wrote:
>> On 15/02/16 17:31, BartC wrote:
>
>>> If there is any translation involved at all from source code to some
>>> other, usually less human-readable format, then both compilers and
>>> interpreters can do that.
>>
>> Interpreting is on-the-fly conversion - decode it *right now* and then
>> do it *right now*. Compilation is conversion into another language for
>> later use.
>
> That would be an unusual - and inefficient - way for an interpreter to 
> work. Very often there is some preprocessing of the whole program or 
> module before execution starts, a step that tends to be transparent so 
> that it looks like it is interpreting source code directly.

Indeed, a program is tokenized and converted to some sort of data
structure like an abstract syntax tree. We don't think of that as
compiling. When you have an AST interpreter, the perspective is that
"I haven't written a compiler for this language yet; it's on the to-do
list".

Back to comp.programming | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

First Program with Python! anitagoyal571@gmail.com - 2016-02-09 06:11 -0800
  Re: First Program with Python! Richard Heathfield <rjh@cpax.org.uk> - 2016-02-09 14:30 +0000
    Re: First Program with Python! Ben Bacarisse <ben.usenet@bsb.me.uk> - 2016-02-09 14:35 +0000
      Re: First Program with Python! Richard Heathfield <rjh@cpax.org.uk> - 2016-02-09 19:06 +0000
        Re: First Program with Python! Öö Tiib <ootiib@hot.ee> - 2016-02-09 16:55 -0800
          Re: First Program with Python! Richard Heathfield <rjh@cpax.org.uk> - 2016-02-10 09:20 +0000
          Re: First Program with Python! Kaz Kylheku <330-706-9395@kylheku.com> - 2016-02-15 16:49 +0000
    Re: First Program with Python! Öö Tiib <ootiib@hot.ee> - 2016-02-09 16:32 -0800
      Re: First Program with Python! BartC <bc@freeuk.com> - 2016-02-10 14:07 +0000
        Re: First Program with Python! David Brown <david.brown@hesbynett.no> - 2016-02-10 16:24 +0100
          Re: First Program with Python! BartC <bc@freeuk.com> - 2016-02-10 16:55 +0000
            Re: First Program with Python! David Brown <david.brown@hesbynett.no> - 2016-02-11 00:18 +0100
              Re: First Program with Python! BartC <bc@freeuk.com> - 2016-02-11 00:07 +0000
          Re: First Program with Python! Kaz Kylheku <330-706-9395@kylheku.com> - 2016-02-15 16:58 +0000
        Re: First Program with Python! Richard Heathfield <rjh@cpax.org.uk> - 2016-02-10 21:51 +0000
          Re: First Program with Python! BartC <bc@freeuk.com> - 2016-02-11 00:15 +0000
  Re: First Program with Python! Kaz Kylheku <330-706-9395@kylheku.com> - 2016-02-15 16:46 +0000
    Re: First Program with Python! BartC <bc@freeuk.com> - 2016-02-15 17:31 +0000
      Re: First Program with Python! Richard Heathfield <rjh@cpax.org.uk> - 2016-02-15 20:16 +0000
        Re: First Program with Python! BartC <bc@freeuk.com> - 2016-02-15 22:45 +0000
          Re: First Program with Python! Kaz Kylheku <330-706-9395@kylheku.com> - 2016-02-16 03:40 +0000

csiph-web