Your message dated Thu, 31 May 2012 10:24:10 +0200
with message-id
<caljhhg_5dofwvbp4gy1af62t5rw1ken8okdvgy-hwoybafv...@mail.gmail.com>
and subject line Re: [php-maint] Bug#674944: php5-common: PHP-5.4.3-5 : No way
to exclude E_STRICT warnings from error reporting
has caused the Debian Bug report #674944,
regarding php5-common: PHP-5.4.3-5 : No way to exclude E_STRICT warnings from
error reporting
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
674944: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674944
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: php5-common
Version: 5.4.3-5
Severity: important
Tags: upstream
I have tried to tweak the error_reporting variable in /etc/php5/apache2/php.ini
to mute warnings about PHP-4 compatibility problems in my Drupal 6.26
installation, without success - the only way I found was to set error_reporting
= 0.
Setting the variable to either E_ERROR or E_WARNING produces the warnings
related to strict-ness violations. The documentation leas one to believe that
E_ALL now includes E_STRICT, but this doesn't seem to be the case, since both
E_ERROR and E_WARNING (values 1 and 2) trigger the warnings.
Is this behaviour really intended, or has a small bug slipped in ?
Thanks for a reply.
-rg-
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'stable-updates'), (300, 'unstable'),
(200, 'stable'), (1, 'experimental')
Architecture: i386 (x86_64)
Kernel: Linux 3.1.0-1-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash
Versions of packages php5-common depends on:
ii dpkg 1.16.3
ii libc6 2.13-32
ii psmisc 22.16-1
ii sed 4.2.1-9
ii ucf 3.0025+nmu3
php5-common recommends no packages.
php5-common suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
notfound 674944 php5/5.4.3-5
thank you
Hi Roger,
On Wed, May 30, 2012 at 8:58 PM, roger crettol <[email protected]> wrote:
> So, error_reporting is correctly set, but still, E_STRICT warnings are
> issued. I believe this is the case whenever E_ERROR or E_WARNING is on. Pls.
> advise.
I think you include some PHP code (some other Drupal module somewhere
perhaps?) which mess with error_reporting, see:
# cat views.php
<?php
class view {
function &load($arg, $reset = FALSE) {
static $cache = array();
return $cache[$arg];
}
}
view::load('name');
?>
# php -n -d 'error_reporting=E_ALL & ~E_STRICT' views.php
# php -n -d 'error_reporting=E_ALL' views.php
Strict Standards: Non-static method view::load() should not be called
statically in /tmp/views/views.php on line 10
I don't think there's a bug at all, thus I am closing the bug. If you
can reproduce the bug on a small test file (and not Drupal
installation with custom modules loaded), feel free to reopen the bug.
Ondrej
--
Ondřej Surý <[email protected]>
--- End Message ---
