Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!news.swapon.de!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Marko Rauhamaa <marko@pacujo.net>
Newsgroups: comp.lang.python
Subject: Re: Reference
Date: Thu, 06 Mar 2014 02:52:38 +0200
Organization: A noiseless patient Spider
Lines: 22
Message-ID: <87mwh45esp.fsf@elektro.pacujo.net>
References: <53144e8d$0$2149$426a74cc@news.free.fr> <1d1dfa1b-b715-4d8f-9c12-f0d3dc1a22c9@googlegroups.com> <85ppm3httu.fsf@benfinney.id.au> <lf2sjk$7d4$1@ger.gmane.org> <20140303155112.46e34ff8@bigbox.christie.dr> <mailman.7666.1393884138.18130.python-list@python.org> <87siqy7whs.fsf@elektro.pacujo.net> <53155c15$0$2923$c3e8da3$76491128@news.astraweb.com> <mailman.7693.1393910647.18130.python-list@python.org> <op.xb75g7ap5079vu@gnudebeest> <roy-A9E76C.21091704032014@news.panix.com> <164d209c-ba5e-449f-bc25-c27ebfb1fc0f@googlegroups.com> <5316b0dc$0$2923$c3e8da3$76491128@news.astraweb.com> <e1fc76f0-a7f4-4e04-8231-30d2b306e898@googlegroups.com> <53176cfe$0$29985$c3e8da3$5496439d@news.astraweb.com> <87mwh475bc.fsf@elektro.pacujo.net> <mailman.7833.1394053296.18130.python-list@python.org> <87bnxk73gb.fsf@elektro.pacujo.net> <mailman.7840.1394055453.18130.python-list@python.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Injection-Info: mx05.eternal-september.org; posting-host="ff5cf27ef3d5b31f034d3b72bdc27a41"; logging-data="28588"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18djEQhJamLc5u6/cWMNXJq"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux)
Cancel-Lock: sha1:8DhHfQjZlxsfcgayY4Y8KZ8fVfw= sha1:Vm3oDKHwfeJCAqAd/Ipt+7OczDY=
Xref: csiph.com comp.lang.python:67902

Ben Finney <ben+python@benfinney.id.au>:

> Marko Rauhamaa <marko@pacujo.net> writes:
>> When I talk about an object's memory address, I'm not referring to
>> what might be revealed by gdb, for example. That is, I'm not talking
>> about the process's virtual address space, nor am I talking about the
>> physical address on the address bus. I can simply define that the
>> object's memory address is whatever id() returns.
>
> Then this does not count as a leaky abstraction. All you're saying is
> that the ‘id(foo)’ result is a representation of the object identity,
> which is entirely at the level of the abstraction. Nothing is leaked.

I wasn't making a point about a leaky abstraction.

I was just saying talking about id() as a memory address isn't all that
bad. It's a bit like rolling down your power windows or turning up the
volume, when there's nothing to roll or turn. There's no risk of getting
your program wrong.


Marko