Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:44258 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 45776 invoked from network); 13 Jun 2009 06:14:00 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 13 Jun 2009 06:14:00 -0000 Authentication-Results: pb1.pair.com header.from=greg@chiaraquartet.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=greg@chiaraquartet.net; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain chiaraquartet.net from 209.85.216.201 cause and error) X-PHP-List-Original-Sender: greg@chiaraquartet.net X-Host-Fingerprint: 209.85.216.201 mail-px0-f201.google.com Received: from [209.85.216.201] ([209.85.216.201:55202] helo=mail-px0-f201.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 09/C1-32591-6A3433A4 for ; Sat, 13 Jun 2009 02:13:59 -0400 Received: by pxi39 with SMTP id 39so18086pxi.29 for ; Fri, 12 Jun 2009 23:13:56 -0700 (PDT) Received: by 10.142.239.11 with SMTP id m11mr1912685wfh.242.1244873636213; Fri, 12 Jun 2009 23:13:56 -0700 (PDT) Received: from monster.local ([76.84.30.125]) by mx.google.com with ESMTPS id 29sm95869wfg.28.2009.06.12.23.13.55 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 12 Jun 2009 23:13:55 -0700 (PDT) Message-ID: <4A3343A1.4060701@chiaraquartet.net> Date: Sat, 13 Jun 2009 01:13:53 -0500 User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070807) MIME-Version: 1.0 To: PHP Developers Mailing List X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: bug 48541 - critical for PHP 5.3 From: greg@chiaraquartet.net (Greg Beaver) Hi, I didn't mark http://bugs.php.net/48541 as critical because it is not a critical bug, but it is critical that this thing be fixed in PHP 5.3. I can do it if someone can answer this question: how do closures uniquely identify themselves? spl_autoload_register is mistakenly treating all closures as if they were a single copy of the static method "Closure::__invoke", and so only the first registered closure is ever called (plus it leaks the other closures at shutdown). If the system can be made to better identify the closure, then spl_autoload_register can use that (and also properly free the refcount on a dupe). Greg