Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:39595 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 46949 invoked from network); 4 Aug 2008 05:06:20 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Aug 2008 05:06:20 -0000 Authentication-Results: pb1.pair.com smtp.mail=stas@zend.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=stas@zend.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zend.com designates 212.25.124.163 as permitted sender) X-PHP-List-Original-Sender: stas@zend.com X-Host-Fingerprint: 212.25.124.163 il-gw1.zend.com Windows 2000 SP4, XP SP1 Received: from [212.25.124.163] ([212.25.124.163:53013] helo=il-gw1.zend.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id BA/00-46562-B4E86984 for ; Mon, 04 Aug 2008 01:06:20 -0400 Received: from us-ex1.zend.com ([192.168.16.5]) by il-gw1.zend.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 4 Aug 2008 08:07:02 +0300 Received: from [192.168.17.27] ([192.168.17.27]) by us-ex1.zend.com with Microsoft SMTPSVC(6.0.3790.3959); Sun, 3 Aug 2008 22:06:59 -0700 Message-ID: <48968E73.405@zend.com> Date: Sun, 03 Aug 2008 22:06:59 -0700 Organization: Zend Technologies User-Agent: Thunderbird 2.0.0.16 (Windows/20080708) MIME-Version: 1.0 To: Etienne Kneuss CC: PHP Internals List , Marcus Boerger References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 04 Aug 2008 05:06:59.0091 (UTC) FILETIME=[EC52FE30:01C8F5EF] Subject: Re: [PHP-DEV] Re: __invoke concerns From: stas@zend.com (Stanislav Malyshev) Hi! > 1) With the interface, the prototype is fixed. That definitely would not work. Interface could leave __invoke undefined, though then it'd be more of documentation/attribute purpose than enforcing having __invoke. But it can be workable. > However, I'd still like to make closures more flexible and > internals-friendly by implementing zend_get_closure as a handler. Hmm... it may work, at least at the first glance I don't see any trouble with it. -- Stanislav Malyshev, Zend Software Architect stas@zend.com http://www.zend.com/ (408)253-8829 MSN: stas@zend.com