Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:16201
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <4280CBE1.1040801@php.net>
Date: Tue, 10 May 2005 10:57:37 -0400
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
MIME-Version: 1.0
To: lpedretti@suserver.com
Cc: internals@lists.php.net
References: <200505091130.56300.lpedretti@suserver.com> <200505101046.19099.lpedretti@suserver.com> <4280C47B.2070507@php.net> <200505101148.56888.lpedretti@suserver.com>
In-Reply-To: <200505101148.56888.lpedretti@suserver.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP] Re: [PHP-DEV] make new return a reference to existent object
From: lsmith@php.net (Lukas Smith)

Leonardo Pedretti wrote:
> Yes, the question was pointed in another way, the destructors are not called 
> until the last reference to an object has been removed, but if you store a 
> reference in an array so you lately return a reference to the already loaded 
> instance instead of creating an aliasing of that instance, then you get the 
> undesirable behavior that the object is never destroyed until the script 
> ends, because there is always a reference in that array and you can not check 
> when references are removed in any way.
> And leaving the array growing while each object that exists in a huge database 
> is slowly loaded and never unloaded, is not an option.

then dont store a reference to the object but instead just store the key 
in the array.

regards,
Lukas