TYPO3 Core

There is something in the core that sets the error reporting to 22519 (E_ALL ^ E_NOTICE ^ E_DEPRECATED), even with the following localconf.php configuration:

$TYPO3_CONF_VARS['SYS']['displayErrors'] = 0;
$TYPO3_CONF_VARS['SYS']['errorHandlerErrors']     = 22517; // E_ALL ^ E_DEPRECATED ^ E_NOTICE ^ E_WARNING (everything except deprecated-msgs and notices and warnings) 
$TYPO3_CONF_VARS['SYS']['syslogErrorReporting']   = 22517; // E_ALL ^ E_DEPRECATED ^ E_NOTICE ^ E_WARNING (everything except deprecated-msgs and notices and warnings) 
$TYPO3_CONF_VARS['SYS']['belogErrorReporting']    = 22517; // E_ALL ^ E_DEPRECATED ^ E_NOTICE ^ E_WARNING (everything except deprecated-msgs and notices and warnings)

This can be reproduced on all systems using TYPO3 4.5.X with PHP 5.3 on Windows and Linux.

Even when set directly in the php.ini, the value get's set to 22519 again.

To check I used extdeveval's phpinfo.

This wouldn't be as much as a problem, if the PHP errors weren't logged to PHP's error log (which can only be avoided by either setting the correct error_reporting bitmask or disabling error reporting completly which should not be seen as an option).

I made absolutely sure that none of the installed extensions in the system actually sets this value by:
- grep'ing the whole thing for 22519, E_WARNING, ini_set and error_reporting
- deinstalling all non-core extensions
- tracing the execution of the extdeveval module

All this showed that there is nothing that actually modifies the error reporting, but still, the error_reporting get's flawnd (see attached screenshot from extdeval).