Hi Nikita, On Thu, May 14, 2015 at 6:51 PM, Nikita Popov <nikita....@gmail.com> wrote:
> The output is a bit confusing: This will actually throw a TypeException, > it's just currently rendered like a fatal error (known issue, will have to > be resolved at some point). If you wrap your code with a catch > (TypeException $e) you'll be able to handle argument type errors - this > includes both errors for user typehints and for internal function types. Thanks again, It even worked on 3v4l http://3v4l.org/sp1C4 Regards, -- Yasuo Ohgaki yohg...@ohgaki.net
