Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:43645 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 78219 invoked from network); 7 Apr 2009 08:39:04 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 Apr 2009 08:39:04 -0000 Authentication-Results: pb1.pair.com header.from=mls@pooteeweet.org; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=mls@pooteeweet.org; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain pooteeweet.org from 88.198.8.16 cause and error) X-PHP-List-Original-Sender: mls@pooteeweet.org X-Host-Fingerprint: 88.198.8.16 bigtime.backendmedia.com Linux 2.6 Received: from [88.198.8.16] ([88.198.8.16:47954] helo=bigtime.backendmedia.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 69/1A-12298-7211BD94 for ; Tue, 07 Apr 2009 04:39:03 -0400 Received: from localhost (unknown [127.0.0.1]) by bigtime.backendmedia.com (Postfix) with ESMTP id 676124144058; Tue, 7 Apr 2009 08:43:16 +0000 (UTC) X-Virus-Scanned: amavisd-new at backendmedia.com Received: from bigtime.backendmedia.com ([127.0.0.1]) by localhost (bigtime.backendmedia.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z6v60UT5DnSM; Tue, 7 Apr 2009 10:43:15 +0200 (CEST) Received: from [10.1.2.126] (46.12.3.213.fix.bluewin.ch [213.3.12.46]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: mls@pooteeweet.org) by bigtime.backendmedia.com (Postfix) with ESMTP id 05BB44144009; Tue, 7 Apr 2009 10:43:14 +0200 (CEST) Cc: PHP internals Message-ID: To: RQuadling@googlemail.com In-Reply-To: <10845a340904070055m262af976ge8db476db38119a0@mail.gmail.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Date: Tue, 7 Apr 2009 10:38:50 +0200 References: <10845a340904070055m262af976ge8db476db38119a0@mail.gmail.com> X-Mailer: Apple Mail (2.930.3) Subject: Re: [PHP-DEV] Closure serialization. From: mls@pooteeweet.org (Lukas Kahwe Smith) On 07.04.2009, at 09:55, Richard Quadling wrote: > Hi. > > Currently you cannot serialize a closure. That certainly makes sense. > > But would it be possible/feasible that a closure could be serialized > if the value returned was the byte code used by the engine to execute > the compiled closure? > > Or is this one of the "don't go there" ideas I sometimes get? I guess its a dont go there thing, as you also run into trouble with "use"-d variables. regards, Lukas Kahwe Smith mls@pooteeweet.org