#40244 [Bgs->Opn]: PHP Strict errors even with E_STRICT Disabled

ID: 40244 User updated by: lists at cyberlot dot net Reported By: lists at cyberlot dot net -Status: Bogus +Status: Open Bug Type: Compile Warning Operating System: Centos 4.4 PHP Version: 5.2.0 New Comment: Your wrong, Try the following <?php $er = error_reporting(0); include('Mail.php'); $mail_object = Mail::factory('smtp'); $mail_object->send('test@test.com','Subject','Body'); ?> If these errors are during compile time, and compile time happens before all this then why does the above code not report the errors? Previous Comments: ------------------------------------------------------------------------ [2007-01-26 15:11:33] tony2001@php.net These messages are generated in compile time, all the functions are executed AFTER that, so error_reporting(0); does not have any effect and this is expected behaviour. ------------------------------------------------------------------------ [2007-01-26 15:04:08] lists at cyberlot dot net They told me to report it to you http://pear.php.net/bugs/bug.php?id=9950 So the 2 "teams" need to get together and figure this out one way or the other. Since this has to do directly with error reporting not disabling warnings, not with the fact that there are warnings I would tend to lean towards the php side of things ------------------------------------------------------------------------ [2007-01-26 09:00:14] tony2001@php.net Please report PEAR issues to PEAR people using PEAR bug tracker: http://pear.php.net Thank you. ------------------------------------------------------------------------ [2007-01-26 01:27:43] lists at cyberlot dot net also if you remove the error_reporting($er); the error goes away, even though that line is after all the other php code. ------------------------------------------------------------------------ [2007-01-26 01:26:01] lists at cyberlot dot net Happens in the newest RC4 release as well ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/40244 -- Edit this bug report at http://bugs.php.net/?id=40244&edit=1