Re: Coercive Scalar Type Hints RFC

On 25/02/15 15:31, Pierre Joye wrote: > With the other RFC, which changes the casting modes, I wish everyone > good luck. I may be wrong, can happen ;), but we simply do not know > and will not know before 7.0.0 is out. Good luck to change them again > to "adapt and tweak", and good luck to the apps developers to adapt > their apps with plenty of patch versions checks. This is the reason #2 > why I am against your RFC, the #1 being the total lack of actual non > magic casting (read: strict), optionally enabled. Like you I don't see the point of the casting changes but similarly I don't see why we have to have strict mode bolted in to everybodys systems as well. Both RFC's seem to be trying to push the bitter pill through with the main payload ... Scalar Type Hinting. There doses seem to be a general assumption that everybody wants STH therefore it has to be included and I am sure that that simple question would get a substantial majority. As with other 'hints' there is a difference in opinion on just what 'everybody' wants. My objection is perhaps to all targeting an different rule sets, none of which actually do the whole job, and now that I am starting to get into just how the code works, I think I can see openings for hook points where just how a particular style of working can be accommodated. Just as the problem with case-sensitive core, if the right 'filter' can be made selectable we can all have what we want. Yes it will result in confusion over what runs where, but equally we can tailor hinting to match a particular set of rules rather than having to live with some other persons preference such as the 'new' casting rules ... -- 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