Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:30439 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 50304 invoked by uid 1010); 4 Jul 2007 12:33:13 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 50289 invoked from network); 4 Jul 2007 12:33:13 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Jul 2007 12:33:13 -0000 Authentication-Results: pb1.pair.com smtp.mail=schultz@widescreen.ch; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=schultz@widescreen.ch; sender-id=unknown Received-SPF: error (pb1.pair.com: domain widescreen.ch from 195.49.42.11 cause and error) X-PHP-List-Original-Sender: schultz@widescreen.ch X-Host-Fingerprint: 195.49.42.11 mail.screenlight.ch FreeBSD 4.8-5.1 (or MacOS X 10.2-10.3) Received: from [195.49.42.11] ([195.49.42.11:59674] helo=screenlight.ch) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 9C/72-30717-7839B864 for ; Wed, 04 Jul 2007 08:33:13 -0400 Received: from [195.49.42.3] (account lars@toolpark.com HELO [192.168.1.168]) by screenlight.ch (CommuniGate Pro SMTP 4.1.8) with ESMTP id 3927048 for internals@lists.php.net; Wed, 04 Jul 2007 14:32:39 +0200 Message-ID: <468B9383.4050105@widescreen.ch> Date: Wed, 04 Jul 2007 14:33:07 +0200 User-Agent: Thunderbird 2.0.0.4 (Windows/20070604) MIME-Version: 1.0 To: internals@lists.php.net References: <468519DC.8060502@widescreen.ch> <4685785E.5010709@zend.com> <585221804.20070701154538@marcus-boerger.de> <468B8F91.2020109@widescreen.ch> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] toString() and Object #ID From: schultz@widescreen.ch (Lars Schultz) > Oh, that clears everything, please ignore my previous post. Still, > don't you think this is a bit misleading? IMHO, new object should > always have the unique id(or hash in terms of spl)... I don't like it either;) But it does exactly what Stanislav Malyshev described: it hashes the "tuple of C pointer". Misleading in this case is that this is only unique as long as the compared objects exist at the same time...then they can't inhabit the same memory-space. But because php clears and reuses memory as soon as no pointers to the object exist (reference counting). In this case php uses the exact same "tuple of C pointer" for the next object as the for the previous one. At least...that's my interpretation of this behaviour;)