Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:43646 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 84515 invoked from network); 7 Apr 2009 08:50:42 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 Apr 2009 08:50:42 -0000 Authentication-Results: pb1.pair.com smtp.mail=guilhermeblanco@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=guilhermeblanco@gmail.com; sender-id=pass; domainkeys=bad Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.44.30 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: guilhermeblanco@gmail.com X-Host-Fingerprint: 74.125.44.30 yx-out-2324.google.com Received: from [74.125.44.30] ([74.125.44.30:46907] helo=yx-out-2324.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id CD/7B-12298-0E31BD94 for ; Tue, 07 Apr 2009 04:50:40 -0400 Received: by yx-out-2324.google.com with SMTP id 3so1633450yxj.83 for ; Tue, 07 Apr 2009 01:50:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=VaPs3uITO9a0fJ4z23M/4YH4V39NUIRIv/QmvwZ+7OM=; b=MZFUo5jdxzWmwnQjKmIOlSC4e9e6xA+TrjPM8QcHkULaETK3bZ/e7MZaEUHc7M4j2f H6HL6vupFP+NWo2OfcmLnoHs/WK+id5noCk3Zl2Pyo74i29TVIsQ+hirfhk2uKyFIAbL yHn85yEj5qUEjLIXxJDmiNHo2Hoj2jNdGk910= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=bos0IoPbO69y9M6xi7qcWs7ZT8gxZ6S3o1IQZ+zF7Z6xLVqYZ73VZgIhk+gJZu6y+M TiG8UVbn4mNDQQWDlHNJeNb03cltD8PyL59tDBUQhs5JbZ/dPROsglZCkzS2un1bzt9q wYQQnKtwz8/mxlPER7mpmwfsH6BbnVSNlb8Bg= MIME-Version: 1.0 Received: by 10.101.71.6 with SMTP id y6mr9245784ank.74.1239094238244; Tue, 07 Apr 2009 01:50:38 -0700 (PDT) In-Reply-To: References: <10845a340904070055m262af976ge8db476db38119a0@mail.gmail.com> Date: Tue, 7 Apr 2009 10:50:38 +0200 Message-ID: To: Lukas Kahwe Smith Cc: RQuadling@googlemail.com, PHP internals Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] Closure serialization. From: guilhermeblanco@gmail.com (Guilherme Blanco) Although this may open a lot of pitfalls, I'd support the idea to serialize Closures. My concern is about recovering a Closure from a user-persisted state. People are able to do weird things, and we should be aware of that. Just need to keep in mind of a dictate that says: "Never underestimate the ignorance of a person". Cheers, On Tue, Apr 7, 2009 at 10:38 AM, Lukas Kahwe Smith wro= te: > > 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 > > > > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > --=20 Guilherme Blanco - Web Developer CBC - Certified Bindows Consultant Cell Phone: +55 (16) 9215-8480 MSN: guilhermeblanco@hotmail.com URL: http://blog.bisna.com S=C3=A3o Paulo - SP/Brazil