Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:87583
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.174 as permitted sender)
To: Bob Weinand <bobwei9@hotmail.com>, Derick Rethans <derick@php.net>
References: <CAMUwpuTRzQHqznqKF-q=1Wy-Xnob9mra748E26YiZMKUa7-4DQ@mail.gmail.com>
 <alpine.DEB.2.20.1508021808550.13034@whisky.home.derickrethans.nl>
 <BLU436-SMTP172F3E282FDEDAA471836F6E2880@phx.gbl>
Cc: Julien Pauli <jpauli@php.net>, PHP Internals <internals@lists.php.net>
Message-ID: <55BFAB53.9050802@gmail.com>
Date: Mon, 3 Aug 2015 10:56:35 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0)
 Gecko/20100101 Thunderbird/38.1.0
MIME-Version: 1.0
In-Reply-To: <BLU436-SMTP172F3E282FDEDAA471836F6E2880@phx.gbl>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Exposing object handles to userland
From: smalyshev@gmail.com (Stanislav Malyshev)

Hi!

> Ehm, you realize that object id is only reset because the old object is freed? As long as the target object is referenced, nothing will have the same object id.

Yes, but if you use it as some sort of ID - e.g. as in "did I already
create a object of class X with parameters stated in class Y" and use
class Y's object ID as a key for that, you're in for a nasty surprise if
some other code deletes that object and creates new object of class Y
with the same ID but completely different content. That's what one of
the code examples referred to in this thread was doing, if I understood
it correctly. Which only goes to emphasize my point - a lot of the
people that want object IDs are either using them wrong or plan to use
them wrong. And wrapping more rope around their necks is not exactly
what we should be doing.

-- 
Stas Malyshev
smalyshev@gmail.com