Breaking character in serialized closure about super_closure HOT 2 CLOSED

I believe you a running into an issue will null bytes. As explained in a note on the PHP manual entry for serialize():

Object's private members have the class name prepended to the member name; protected members have a '*' prepended to the member name. These prepended values have null bytes on either side.

SuperClosure has never done anything to prevent those null bytes from being included in the serialized string. For example, if you serialize a closure that has an object with private members as one of it's context variables, you would've hit the same problem with any version of SuperClosure. It's your responsibility to take the serialized data, and format it for the purpose of whatever you are doing with it. In your case, it sounds like doing a base64_encode() would be a good idea.

The latest beta of SuperClosure includes the Serializer object in the serialization, which does have private members, and would definitely output null bytes. That is why you are running into issues now. However, I've just made a change that removes the need to serialize the Serializer. With that commit, the symptom of your problem should disappear, but your actual problem still remains.

from super_closure.

That explains a lot. Thanks. I will definitely use base64 as this will prevent future issues in this area.

from super_closure.