Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:39200 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 21058 invoked from network); 22 Jul 2008 20:50:17 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 22 Jul 2008 20:50:17 -0000 Authentication-Results: pb1.pair.com smtp.mail=helly@php.net; spf=unknown; sender-id=unknown Authentication-Results: pb1.pair.com header.from=helly@php.net; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 85.214.94.56 as permitted sender) X-PHP-List-Original-Sender: helly@php.net X-Host-Fingerprint: 85.214.94.56 aixcept.net Linux 2.6 Received: from [85.214.94.56] ([85.214.94.56:38865] helo=h1149922.serverkompetenz.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 93/B2-04511-80846884 for ; Tue, 22 Jul 2008 16:50:17 -0400 Received: from MBOERGER-ZRH (ip131.fa1-0-1.occ.iinet.com [198.145.32.131]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by h1149922.serverkompetenz.net (Postfix) with ESMTP id F10E511F068; Tue, 22 Jul 2008 22:50:12 +0200 (CEST) Date: Tue, 22 Jul 2008 22:50:07 +0200 Reply-To: Marcus Boerger X-Priority: 3 (Normal) Message-ID: <1332388256.20080722225007@marcus-boerger.de> To: Stanislav Malyshev CC: Lukas Kahwe Smith , PHP Developers Mailing List , In-Reply-To: <48863E2B.8040001@zend.com> References: <8A5D4032-1FC4-44BB-90F3-61B802F10159@pooteeweet.org> <6BD46F4A-2733-4160-9A3E-AD49F3002865@pooteeweet.org> <48863E2B.8040001@zend.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] closures questions From: helly@php.net (Marcus Boerger) Hello Stanislav, Tuesday, July 22, 2008, 10:08:11 PM, you wrote: > Hi! >> so do we even want the toString() method? > IMHO we should drop toString from Closure. Sam here. It makes no sense anyway. This mail thread just proved that. >>> Maybe it could return some relevant information for exporting the >>> closure across >>> data >> >> not a huge biggy to me. > I don't think Closure can be meaningfully exported. Can we prohibit it? We could add a special case that disallows it. >> I guess this is a draw back from the OO approach (rather than the >> original resource approach), but solvable? > I think we can make working clone there - just copy all data, etc. Yep, it should be possible. On the other hand, we probably would like to change the bound variables then which brings us to having to support properties. Hey, didn't we just disable that? Best regards, Marcus