Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:26896 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 82839 invoked by uid 1010); 11 Dec 2006 09:18:04 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 82810 invoked from network); 11 Dec 2006 09:18:04 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 Dec 2006 09:18:04 -0000 Authentication-Results: pb1.pair.com header.from=mp@webfactory.de; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=mp@webfactory.de; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain webfactory.de from 195.227.108.51 cause and error) X-PHP-List-Original-Sender: mp@webfactory.de X-Host-Fingerprint: 195.227.108.51 wfserver02.wf-ppr.de Windows 2000 SP2+, XP SP1 (seldom 98 4.10.2222) Received: from [195.227.108.51] ([195.227.108.51:42577] helo=wfserver02.wf-ppr.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 94/10-10294-6312D754 for ; Mon, 11 Dec 2006 04:14:01 -0500 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5 Date: Mon, 11 Dec 2006 10:11:56 +0100 Message-ID: <00A2E2156BEE8446A81C8881AE117F1949C80E@companyweb> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [PHP-DEV] Re: [RFC] Magic Method that handles unset($object) Thread-Index: Acccs29SLeEW+tuYQpqdiDjbrMtoggATeTkg To: "Ants Aasma" , Subject: AW: [PHP-DEV] Re: [RFC] Magic Method that handles unset($object) From: mp@webfactory.de ("Matthias Pigulla") =20 > -----Urspr=FCngliche Nachricht----- > Von: Ants Aasma [mailto:ants.aasma@gmail.com]=20 > That would indeed be too slow. The standard way to handle=20 > this, is to only check visibility periodically. That is how=20 > Java, .NET, Python and countless others do that. Check=20 > http://www.hpl.hp.com/personal/Hans_Boehm/gc/ for a sample of=20 > how an implementation might look like. The whole issue comes up regularly on various lists, e. g. Propel or = Phing suffer from it. Also see http://bugs.php.net/bug.php?id=3D33595. = Working around this in userland may be possible but is at least painful = and messy. If the only problem is that detection is slow, wouldn't it be possible = to add a gc_cleanup() function that performs the scan? Those who use PHP = in a request/response environment need not care (everything is freed at = the end of the request). Those who don't and hit the problem regularly = will find a good place to make this call and certainly won't complain = about the delay.=20 mp.