A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2003-August/037500.html below:

[Python-Dev] sizeof(long) != sizeof(void*)

[Python-Dev] sizeof(long) != sizeof(void*) [Python-Dev] sizeof(long) != sizeof(void*)Tim Peters tim.one at comcast.net
Wed Aug 6 16:37:25 EDT 2003
[Samuele Pedroni]
> but that something like id() can be cheaply offered/exposed is very
> much a characteristic of the underlying GC implementation that is
> being exploited (objects don't move),

The docs for id() just promise a unique integer; it needn't be a memory
address.

> and the GC impl is an overall implementation detail.
>
> I have just gone through implementing a correct id() for Jython.
>
> For the serious usage id() would be better substituted by an identity
> mapping implementation

Sorry, I don't know what that means, and a unique integer seems to be what
most users of id() are looking for.

> which initially for CPython could simply be using id(). But the user would
use
> that and not rely on id().

As above, the identity-mapping business lost me.

> ...


More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4