Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder1.news.weretis.net!feeder.erje.net!eu.feeder.erje.net!newsfeed.freenet.ag!news2.euro.net!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
Date: Sun, 16 Jun 2013 17:02:09 +0200
From: Andreas Perstinger <andipersti@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: python-list@python.org
Subject: Re: OT: C vs Python terminology
References: <2bc90d3b-09c2-4315-9357-ff7f039465e0@googlegroups.com> <kp9lcd$9l5$1@news.ntua.gr> <51b926a3$0$29997$c3e8da3$5496439d@news.astraweb.com> <kpbraq$qvk$6@news.ntua.gr> <mailman.3184.1371126194.3114.python-list@python.org> <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> <51BD9FDC.8050006@gmail.com> <51BDB5B6.6020900@davea.name>
In-Reply-To: <51BDB5B6.6020900@davea.name>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.3445.1371394941.3114.python-list@python.org>
Lines: 49
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:48458

On 16.06.2013 14:55, Dave Angel wrote:
> On 06/16/2013 07:22 AM, Andreas Perstinger wrote:
>> On 16.06.2013 08:32, Denis McMahon wrote:
>>> C:
^^^^^^^^^

>>>
>>> int a, b;
>>> b = 6;
>>> a = b;
>>>
>>> In C, this places the numeric value 6 into the memory location identified
^^^^^^^^^^^^^

>>> by the variable "b",
>>
>> so far so good.
>>
>>> then copies the value from the location pointed to by "b" into the
>>> location pointed to by "a".
>>
>> Wrong. Neither "a" nor "b" are pointers, thus they don't point to a
>> memory location.
>> This part should be written as
>> "then copies the value at the location identified by "b" to the location
>> identified by "a".
>
> But it doesn't.  It binds b to the same object to which a is currently
> bound.

Are you aware that Denis was talking about the behaviour of C in the 
above quote?

>>> b is a pointer to a memory location containing the value 6
>>  > a is a pointer to another memory location also containing the value 6
>>
>> Again, neither "a" nor "b" are pointers.
>> "b" is the name of a memory location containing the integer value 6.
>> "a" is the name of another memory location containing the integer value 6.
>>
>
> Not even close.  If you don't like the terms "bound" or "points", the
> perhaps you'd be happy with "b" is the name that currently knows how to
> find an int object containing 6.  That object has no name, and never
> will.  And it can exist for a long time with no names directly bound to it.

Again, Denis was talking about C.

Bye, Andreas