Hi all, On Sat, Apr 9, 2016 at 8:07 AM, lucas at threeamdesign dot com dot au <php-b...@lists.php.net> wrote: > Edit report at https://bugs.php.net/bug.php?id=69959&edit=1 > > ID: 69959 > Comment by: lucas at threeamdesign dot com dot au > Reported by: lucas at threeamdesign dot com dot au > Summary: unserialize() needlessly requires boilerplate > Status: Suspended > Type: Feature/Change Request > Package: *General Issues > PHP Version: 7.0.0alpha2 > Block user comment: N > Private report: N > > New Comment: > > I'm sure you're time poor, but it seems you haven't really read my proposal. > I offered a perfectly sound and *completely backwards-compatible* solution. > > Adding an *optional* second parameter, that is a reference to whether the > deserialization was successful, means the function's return value can stay > the same, thus no updates are required to userland code. This mirrors the > behaviour of `exec` where the shell return value is not the return value of > the function.
Last comment sounds reasonable. How about add 2nd parameter to unserialize()? Re-open this bug report? What is your thoughts? Regards, -- Yasuo Ohgaki yohg...@ohgaki.net -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
