ID: 34009
Updated by: [EMAIL PROTECTED]
Reported By: ast at gmx dot ch
-Status: Open
+Status: Assigned
Bug Type: Scripting Engine problem
Operating System: Gentoo Linux
PHP Version: 4.4.0
-Assigned To:
+Assigned To: Derick
New Comment:
I will not reply since I don't use PHP 4 anymore.
Assigned to Derick who likes it so much and loves to fix reference
bugs! :)
Previous Comments:
------------------------------------------------------------------------
[2005-09-16 19:04:54] ast at gmx dot ch
[EMAIL PROTECTED]:
I have yet another ISP claiming that their PHP 4.4.0 is ok, but the
code is wrong (Notices showing up when they shouldn't).
Could you please reply to my point "1." from message "[7 Aug 2:32pm
CEST] ast at gmx dot ch"? I'd like to make sure that we agree that the
code is correct. A lot of servers running PHP 4.4.0 don't show notices
which indicates it's correct code and my mind tells me it's correct.
Also, do you think John Lim from the adodb project is right with his
theory that 3rd party PHP extensions could be the issue. Or maybe some
C libraries?
See the message from "[8 Aug 10:48am CEST] ast at gmx dot ch".
Thank you very much.
- Andy
------------------------------------------------------------------------
[2005-08-08 13:51:22] ast at gmx dot ch
The reproduce script starts with:
error_reporting(E_ALL);
And even if not all of the tested systems have a default
error_reporting level of E_ALL, some of them have and don't show / show
the Notice.
I'd disagree, it should not be return &$false; That would even give a
parse error.
But that's offtopic.
If you think it should give a Notice with error_reporting = E_ALL for
the reproduce script, please try it. On most systems, it doesn't return
a Notice.
Bottom line:
I hope after reading the report carefully you'll understand the issue
and agree with [EMAIL PROTECTED] and me that it shouldn't show a Notice in
either of the cases.
One of the ISPs is still trying to figure out why it gives the Notice,
I guess the next step will be to disable all extensions etc.
------------------------------------------------------------------------
[2005-08-08 13:25:57] [EMAIL PROTECTED]
No, whatever you may think all test cases do NOT have E_ALL set.
The two phpinfo URLs listed under your "Unexpected result observed on"
have error_reporting = E_ALL (2047).
The URL listed under "Correct behaviour observed on" has
error_reporting set to 2039 (E_ALL ^ E_NOTICE).
It's a Notice. You get it when E_NOTICE is enabled and not when it
isn't. QED
(And yes, I personally think it's a correct Notice; the return line
should be "return &$false" to not get a Notice, surely? But maybe I'm
wrong about that....)
------------------------------------------------------------------------
[2005-08-08 12:58:48] ast at gmx dot ch
[EMAIL PROTECTED]:
So you say with error_reporting = E_ALL it *should* give a Notice in
this case?
If so, no offence, but I think you haven't read the bug report
carefully. All tested systems have error_reporting E_ALL. The point is
that even with E_ALL, it doesn't give a Notice on most systems (and I
think that's correct), but others do.
But we're now at a point where we think that 3rd party extensions
could be responsible for the incorrect behavior.
------------------------------------------------------------------------
[2005-08-08 12:51:54] [EMAIL PROTECTED]
There's no fault in the code or PHP. It's the server setup differing.
(Strong Hint: look at the value of error_reporting on each of the
phpinfo pages you quoted.)
------------------------------------------------------------------------
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/34009
--
Edit this bug report at http://bugs.php.net/?id=34009&edit=1
