On 27 July 2013 15:58, Jakub Zelenka wrote:
>>
>> > Alternatively, could the problem perhaps be mitigated by making
>> > available some utility functions for serializing native types?
>>
>> We could definitely make some parts of serializer API-accessible, or
>> even make serializer as a whole to b
On Mon, Jul 29, 2013 at 12:01 PM, Andrey Hristov wrote:
> Hi,
> after experiencing again warnings about conversion from const char * to
> char * when calling some PHP API functions I decided to spend some time and
> constify a few of these. The result is a patch that constifies the Streams
> API
Hi
What's about unserialization?
>
Yeah that's actually a good point! :) It could be handled by implicit
object unserialization if the unserialize callback is NULL. However this is
not optimal for performance and also create properties in the object which
doesn't have to be necessary. There shoul
