Re: [PHP-DEV] New functions `hash_serialize` and `hash_unserialize`?

ized > system. Please be careful when opening attachments, clicking links, or > following instructions. For more information, visit the HUIT IT Portal and > search for SPF. > -- > On Thu, Jun 11, 2020 at 11:59 AM Eddie Kohler > wrote: > >> Than

Re: [PHP-DEV] New functions `hash_serialize` and `hash_unserialize`?

Thanks for this suggestion. I've updated the implementation to make HashContext implement Serializable. I'd still be grateful for more feedback, or perhaps I should just create an RFC? Eddie On Mon, Jun 8, 2020 at 9:28 AM Johannes Schlüter wrote: > On Mon, 2020-06-08 at 09:01

Re: [PHP-DEV] Session default settings (use_strict_mode)

Enabling same-site cookies by default is a little risky now, because current browsers don't always set them properly. https://bugs.chromium.org/p/chromium/issues/detail?id=961617 On Sun, Jun 7, 2020 at 6:42 PM Claude Pache wrote: > > > > Le 7 juin 2020 à 22:15, AllenJB a écrit : > > > > Are t

[PHP-DEV] New functions `hash_serialize` and `hash_unserialize`?

well, and simplify implementation, but it's possible that `__serialize/__unserialize` or the internal `serialize/unserialize` functions would be preferred. I'd be grateful for any feedback. Thanks! Eddie Kohler

Re: [PHP-DEV] Re: Proposed change in json_encode+JSON_UNESCAPED_UNICODE behavior

Yes, without the JSON_UNESCAPED_UNICODE flag, all characters with Unicode values >= 0x80 are escaped. That's the default behavior. On Tue, Jan 5, 2016 at 2:45 PM, Andrea Faulds wrote: > Hi Eddie, > > Eddie Kohler wrote: >> >> The U+2028 LINE SEPARATOR a

[PHP-DEV] Proposed change in json_encode+JSON_UNESCAPED_UNICODE behavior

https://github.com/php/php-src/pull/1701>, but since it is a small change in behavior, he asked me to email internals in case anyone objects. Thanks all, Eddie Kohler -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php