Re: filtered unserialise() - results

Hi! > Sorry, I missed this thread back when you posted. > Personally I'm a bit hesitant about this change. > Do we already have something additional/upcoming features which could be > a good fit to lump together with allowed_classes? There was talk about limiting depth or breadth to prevent hash DoS attacks, etc. While I myself do not plan to work on it in near future, after some though I decided it does not hurt to provide this opportunity. The added benefit is, given no named parameters syntax yet, this is a good way to introduce people reading the code to the meaning of the feature - ["allowed_classes" => ...] would be pretty obvious about what this does. -- Stas Malyshev smalyshev@gmail.com