Re: Coercive STH - some real world tests and updated RFC

On 27/02/15 14:15, Benjamin Eberlei wrote: > Imho the problem is that the return values of php internal functions being > string|false will lead to massive consecutive errors when passing this on > to other internal functions. This is perhaps the crux of my objection to both types of 'error checking' ... OK the return should be an empty string rather than false, but certainly one does not want an exception when nothing is returned. So much code IS based on doing one thing if there is a value and another when there is not, so if that is the problem people are claiming needs fixing perhaps that is what needs addressing? string|false is a core element of most of PHP? -- 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