Path: csiph.com!fu-berlin.de!uni-berlin.de!not-for-mail
From: Dennis Lee Bieber <wlfraed@ix.netcom.com>
Newsgroups: comp.lang.python
Subject: Re: Assignment Versus Equality
Date: Mon, 27 Jun 2016 20:11:40 -0400
Organization: IISS Elusive Unicorn
Lines: 26
Message-ID: <mailman.49.1467072707.2358.python-list@python.org>
References: <8a53c069-ca13-47bf-a24e-d2393a018b22@googlegroups.com> <nkobtu$gaq$1@dont-email.me> <l8svmbdf95jh54nmal5h3130cgmhreo3ot@4ax.com> <mailman.4.1466954526.2358.python-list@python.org> <nkotei$dk9$1@dont-email.me> <nkotv4$fif$1@dont-email.me> <nkrbgb$oc5$1@ger.gmane.org> <f62db73a-55c9-8007-1edd-e9b2b1b314b5@mrabarnett.plus.com> <mailman.37.1467041247.2358.python-list@python.org> <65309b66-485d-4be7-94ca-f9a8f58b513a@googlegroups.com> <nksbkk$q53$1@dont-email.me> <svf3nb5r72vb0nmceiaiccl782k48l0hrd@4ax.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Trace: news.uni-berlin.de 9F8hglp2PYscZoOlr6BUpQ25ByG2oGIBHD+jW7OCktFg==
Return-Path: <python-python-list@m.gmane.org>
X-Original-To: python-list@python.org
Delivered-To: python-list@mail.python.org
X-Spam-Status: OK 0.002
X-Spam-Evidence: '*H*': 1.00; '*S*': 0.00; 'compiler': 0.05; 'ast': 0.09; 'message-id:@4ax.com': 0.09; 'received:80.91': 0.09; 'received:80.91.229': 0.09; 'received:gmane.org': 0.09; 'received:list': 0.09; 'term,': 0.09; 'output': 0.13; '(),': 0.16; '2016': 0.16; 'compile,': 0.16; 'ie.': 0.16; 'messy': 0.16; 'received:80.91.229.3': 0.16; 'received:io': 0.16; 'received:plane.gmane.org': 0.16; 'received:psf.io': 0.16; 'processor': 0.18; 'url:home': 0.18; 'machine': 0.21; 'suppose': 0.22; 'decide': 0.23; 'header:X-Complaints-To:1': 0.26; 'followed': 0.27; 'other,': 0.29; 'array': 0.29; 'code': 0.30; 'possibly': 0.32; 'statement': 0.32; 'case,': 0.34; 'tue,': 0.34; 'next': 0.35; 'could': 0.35; 'feed': 0.35; 'knowledge': 0.35; 'but': 0.36; 'loaded': 0.36; 'to:addr:python-list': 0.36; 'subject:: ': 0.37; 'being': 0.37; 'received:org': 0.37; 'charset :us-ascii': 0.37; 'things': 0.38; 'doing': 0.38; 'format': 0.39; 'to:addr:python.org': 0.40; 'mark': 0.40; 'back': 0.62; 'statement,': 0.66; 'cards': 0.67; '>you': 0.84; 'dennis': 0.91; 'received:108': 0.93
X-Injected-Via-Gmane: http://gmane.org/
X-Gmane-NNTP-Posting-Host: adsl-108-68-176-19.dsl.klmzmi.sbcglobal.net
X-Newsreader: Forte Agent 6.00/32.1186
X-No-Archive: YES
X-BeenThere: python-list@python.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: General discussion list for the Python programming language <python-list.python.org>
List-Unsubscribe: <https://mail.python.org/mailman/options/python-list>, <mailto:python-list-request@python.org?subject=unsubscribe>
List-Archive: <http://mail.python.org/pipermail/python-list/>
List-Post: <mailto:python-list@python.org>
List-Help: <mailto:python-list-request@python.org?subject=help>
List-Subscribe: <https://mail.python.org/mailman/listinfo/python-list>, <mailto:python-list-request@python.org?subject=subscribe>
X-Mailman-Original-Message-ID: <svf3nb5r72vb0nmceiaiccl782k48l0hrd@4ax.com>
X-Mailman-Original-References: <8a53c069-ca13-47bf-a24e-d2393a018b22@googlegroups.com> <nkobtu$gaq$1@dont-email.me> <l8svmbdf95jh54nmal5h3130cgmhreo3ot@4ax.com> <mailman.4.1466954526.2358.python-list@python.org> <nkotei$dk9$1@dont-email.me> <nkotv4$fif$1@dont-email.me> <nkrbgb$oc5$1@ger.gmane.org> <f62db73a-55c9-8007-1edd-e9b2b1b314b5@mrabarnett.plus.com> <mailman.37.1467041247.2358.python-list@python.org> <65309b66-485d-4be7-94ca-f9a8f58b513a@googlegroups.com> <nksbkk$q53$1@dont-email.me>
Xref: csiph.com comp.lang.python:110621

On Tue, 28 Jun 2016 00:08:00 +0100, BartC <bc@freeuk.com> declaimed the
following:

>
>You just design the compiler to do the same processing in each case, ie. 
>parse a <name> followed (<expression>), then mark the result AST 
>fragment as either an Array term, or Format statement, depending on what 
>follows, and whether the name is "format".
>
	You're expecting an AST in a compiler from the 50s?

	That might have involved having to punch an output deck of cards for
each compile, only to then feed that deck back into the reader for the next
phase of compilation.


>I suppose the compiler could decide to backtrack and re-parse based on 
>the knowledge that is one or the other, but that's a messy way of doing it.

	But kept things to one statement at a time, with the output being the
machine code for the processor -- possibly being punched to cards so it
could be loaded later.
-- 
	Wulfraed                 Dennis Lee Bieber         AF6VN
    wlfraed@ix.netcom.com    HTTP://wlfraed.home.netcom.com/