April 10, 2019 09:email@example.com (Robert Hickman)
> On the balance of things, I would most certainly like to see leading and
> trailing whitespace render a string ineligible to be implicitly
> converted, but I'd be satisfied with (int)" 123 " converting without error.
Given that PHP seems to be gradually moving towards more type
strictness, would it make more sense to move this functionality to a
'parse_numeric_string()' function? Js has parseInt() and parseFloat()
with similar functionality.