Re: com php-src: Add optional second arg to unserialize(): ext/standard/basic_functions.c ext/standard/tests/serialize/serialization_error_001.phpt
ext/standard/tests/serialize/unserialize_consumed.phpt ext/standard/var.c
| From: | Ferenc Kovacs | Date: | Wed, 11 Jun 2014 08:05:16 +0000 |
| Subject: | Re: com php-src: Add optional second arg to unserialize(): ext/standard/basic_functions.c ext/standard/tests/serialize/serialization_error_001.phpt ext/standard/tests/serialize/unserialize_consumed.phpt ext/standard/var.c |
||
| References: | 1 2 3 4 5 6 7 8 9 10 11 12 13 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-74842@lists.php.net to get a copy of this message | ||
On Wed, Jun 11, 2014 at 9:48 AM, Michael Wallner <mike.php.net@gmail.com>
wrote:
>
> On 11 06 2014, at 09:36, Ferenc Kovacs <tyra3l@gmail.com> wrote:
>
> On Tue, Jun 10, 2014 at 7:41 PM, Sara Golemon <pollita@php.net> wrote:
>
> On Tue, Jun 10, 2014 at 10:29 AM, Ferenc Kovacs <tyra3l@gmail.com> wrote:
>
> (And session_encode/decode is even more pita because it only allows
> encoding
>
> from/decoding to a superglobal, so if you wanna parse arbitrary sessions,
> you can't do it without global side effects)
>
> Again, clowny, but unrelated to the topic at hand.
>
>
> sorry, it's one of my pet peeves
>
>
> I think “clowny" was meant in regard to the session serialization
> behaviour.
>
hehe, I also interpreted that way (and my reply meant that the current
session_encode/decode behavior really irks me), but now that you mention,
there is a second (hilarious) interpretation of my mail. :P
--
Ferenc Kovács
@Tyr43l - http://tyrael.hu