Closure serialization. View as Markdown

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,

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

--

--
Guilherme Blanco - Web Developer
CBC - Certified Bindows Consultant
Cell Phone: +55 (16) 9215-8480
MSN: guilhermeblanco@hotmail.com
URL: http://blog.bisna.com
São Paulo - SP/Brazil

Hi,

Currently you cannot serialize a closure. That certainly makes sense.
[...]
I guess its a dont go there thing, as you also run into trouble with
"use"-d variables.

In the long run, I guess, we should try to reach it. Ignoring the use
stuff there were some ideas floating in the past, like storing the
source or using APC or ... but not with 5.3.

johannes