On 16/03/15 06:22, Xinchen Hui wrote: >> It's in the RFC: "Whether or not the function being called was >> > declared in a file that uses strict or weak type checking is >> > irrelevant. The type checking mode depends on the file where the >> > function is called." > my fault, I must oversight of reading this...
If the third party library has been 'converted' to strict, and is expecting strict typing to pick up the sort of conversions that the strict camp want to protect against then there are handlers for that error, but if it is called from a situation where weak conversions are all that is being passed would it be necessary to add back in weak error handling as well if the library is not actually designed to handle those cases? I know all of this has been said a thousand times, but we do not CURRENTLY have type hinting, if projects are going to start relying on weak hinting or strict hinting, then is there any guarantee that there will not be new edge cases when mixing the two methods of working. Add in the fact that we do not HAVE to use it so the calling project may simply not be bothering about hinting at all? But now has to handle new errors which start when a library adds any hinting? -- 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
