> -----Original Message----- > From: Stas Malyshev [mailto:smalys...@sugarcrm.com] > Sent: Thursday, July 17, 2014 9:08 AM > To: Laruence; Remi Collet > Cc: PHP Internals > Subject: Re: [PHP-DEV] An BC issue in unserialize > > Hi! > > > in such case, the serialized data could be shared by 5.5 and 5.6... > > This is true, but what you presented is not serialized data. Serialized > data will > be fine. But the code you shown instead tries to use serializer as a > roundabout > way of instantiating objects. This is not the right thing to do, this was > never the > purpose of the serializer and was never guaranteed to work.
My key concern is that I've now bumped into two applications - both OroCRM and also Taskada - that work fine with 5.5 but stop working with 5.6 because of that issue. Both are Symfony apps so it might be something that can be solved centrally in Symfony, but it may also be just coincidence. Either way, it's an indication that this would make upgrading to 5.6 harder than it needs to be, and a key tenet of our yearly release cycle was guaranteed pain-free upgrades. IMHO this isn't something we should change in a 2nd digit release, but on a major version, even if it wasn't documented. Zeev -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
