Andrew
- Original Message -
From: "jjt" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, December 26, 2001 1:53 AM
Subject: Re: [PHP] Client side fatal PHP error
> Ah yes... that would do it. How embarrassing! But another respondent
brought
> up an inte
At 08:53 PM 12/25/01 -0500, jjt wrote:
>Why does this error not show up every time?
It will show up every time PHP attempts to call the (incorrect) function. But the
functions won't be called every time.
For example, due to short-circuit evaluation, if the string is "B" or "P", the error
will
> Ah yes... that would do it. How embarrassing! But another respondent brought
> up an interesting question. Why does this error not show up every time? As
> written, it is a basic syntactical error. I tested this thing up and down; I
> test it in production every day.
This error will happen ever
> Is there a utility out there that checks for typos, like a spell check but
> for code? They are the most annoying things ever and probably the hardest of
> errors to find in scrips.
> Something simple, even command line would be handy.
It's good to program with error_reporting turned all the wa
Ah yes... that would do it. How embarrassing! But another respondent brought
up an interesting question. Why does this error not show up every time? As
written, it is a basic syntactical error. I tested this thing up and down; I
test it in production every day.
Ah it's always something th
Yeah,
I know it's executed client side, but if the buffer fills up because you
have a lot to send to the client (and the network connection is saturated),
then it might fail, since it cannot do the test. it is unlikely, but
possible. Also, that code you quoted is (out of context) inefficient, so
Is there a utility out there that checks for typos, like a spell check but
for code? They are the most annoying things ever and probably the hardest of
errors to find in scrips.
Something simple, even command line would be handy.
Also, its interesting that only one user of the script got the erro
> "Call to unsupported or undefined function srtoupper() in on line 82."
srt != str (typo).
> if (strtoupper(substr($xmbrcode,11,1)) != "B" &&
> strtoupper(substr($xmbrcode,11,1)) != "P" &&
> srtoupper(substr($xmbrcode,11,1)) != "H" &&
> srtoupper(substr($xmbrcode,11,1)) != "O"
ext* would help.
>
>Regards,
>
>James Cox
>
>> -Original Message-
>> From: jjt [mailto:[EMAIL PROTECTED]]
>> Sent: Tuesday, December 25, 2001 6:36 PM
>> To: [EMAIL PROTECTED]
>> Subject: [PHP] Client side fatal PHP error
>>
>>
>>
,
James Cox
> -Original Message-
> From: jjt [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, December 25, 2001 6:36 PM
> To: [EMAIL PROTECTED]
> Subject: [PHP] Client side fatal PHP error
>
>
> A visitor to my site repeatedly receives a fatal error in one of
> my sc
A visitor to my site repeatedly receives a fatal error in one of my scripts.
He is using a Compaq PC with IE 6; Windows 98. He gets this error message:
"Call to unsupported or undefined function srtoupper() in on line 82."
Line 82 is a compound IF statement which uses strtoupper(). As best I
11 matches
Mail list logo
