@nicolas-grekas this is for you to review :)

What about defining theE_STRICT constant in the PHP 5.4 polyfill (or do we already do that?)? Then we could already simplify the code in previous versions.

E_ALL has a different meaning in PHP 5.3 and >= 5.4. That is problem. So we cannot do anything in Polyfill.

@Tobion I see, but then treating-1 now likeE_ALL could become tricky in the future (see my inline comment), couldn't it?

Since PHP 7 introduced exceptions in the core, I seriously doubt that any newE_* will ever be introduced.
👍 for me

Thank you@Tobion.

I thought symfony always usednull for default values out of principle, like PHP does, so people can skip them by passing null. This breaks that principle. ;(

Neither symfony nor php itself uses null by default when it doesn't make sense. E.g.http://php.net/manual/en/function.trigger-error.php

PHP does in other cases, where the param might end up being an int though.

Meh. I'm inclined to agree with you I guess.