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 <m...@pooteeweet.org> wrote: > > 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 > m...@pooteeweet.org > > > > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > -- Guilherme Blanco - Web Developer CBC - Certified Bindows Consultant Cell Phone: +55 (16) 9215-8480 MSN: guilhermebla...@hotmail.com URL: http://blog.bisna.com São Paulo - SP/Brazil -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
