On 02/03/15 09:47, Zeev Suraski wrote: > I'm obviously biased but I believe that the coercive rules actually cover a > lot more ground than the weak+strict sets. In other words, with > weak+strict, overall, you're going to have to add custom code in a lot more > cases than with the coercive rule set (either because weak is too weak and > strict will very frequently be too strict, while coercive provides a > rule-set that accepts sensible values and reject non-sensible ones, making > it work out of the box in most cases). But even with coercive, it's > definitely not a one size fits all solution, and it's not supposed to be > either. You still have custom code available to you.
But since the horse is now out of the stable, we have to live with strict anyway, so where will coercive rules fit in if they get accepted as well? All of this is just creating different rules for sub-sets of users :( -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
