Re: Re: Bug #1401 Updated: Script dies during large outputs, sometimes with bogus parser error.
| From: | Jordan Husney | Date: | Thu, 13 May 1999 06:41:11 +0000 |
| Subject: | Re: Re: Bug #1401 Updated: Script dies during large outputs, sometimes with bogus parser error. | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-5594@lists.php.net to get a copy of this message | ||
Fantastic, the bug now seems to be moody. I was getting a parser
error not but three hours before this message. However the symptom of the
bug remains: incomplete output (without an explaination) from the
database.
Are there any internals I could look at?
Jordan.
On Thu, 13 May 1999, Rasmus Lerdorf wrote:
> > I checked the status on the bug, to see if any addional notes had
> > been made-- and found it closed! I am hoping that you will persue this
> > problem, as I do feel it is a genuine php bug.
> > If there is anything I can do to help narrow this problem, please
> > let me now.
> >
> > I did strip out the html, etc. Please see my previous message.
>
> You need to provide a much better example that shows the bug. I have
> tried the URL you gave a half dozen times and have yet to see a PHP
> parser error message like you said.
>
> I am using: http://www.remotepoint.com/~jordanh/half_stats.php3
>
> And I specify more than 600 in the limit box and always see this output at
> the end:
>
> 0Cooked Function: $half_rec[$i]->cooked[$k] =
> $half_rec[$i]->cook_playertime();
>
> 0.05 hrsCooked Function: $half_rec[$i]->cooked[$k] =
> $half_rec[$i]->cook_weapon();
>
> 9mm Assault Rifle187
> jirraCooked Function: $half_rec[$i]->cooked[$k] =
> $half_rec[$i]->cook_frags();
>
> No parser error there. PHP is doing exactly what it is supposed to do
> given your script.
>
> Now, it may be that it isn't doing what you think it should do, but that
> is an entirely separate issue. You said it threw a parser error and it
> doesn't. If your problem is different, then you need to explain that
> explicitly. I suspect you are confused about those ugly eval() calls you
> have in there. I see no reason for using an eval() there and I think what
> you really meant to ask was how to do that assignment instead. But it
> definitely does not look like a PHP bug to me, and thus the bug report has
> been closed.
>
> -Rasmus
>
----------------------------------------------------------------------
Words of Wisdom:
o "They say I'm lazy, but it takes all my time,"
- Joe Walsh, *Life's Been Good*
o Eat your matzo-ball soup! Its good for you!
o Caring is only a function of people who cannot be held
accountable.
o The sooner you fall behind, the more time you have to catch up.
o To steal ideas from one person is plagiarism; to steal from many
is research.
o Remember: 37.2 percent of all statistics are made up on the spot!
----------------------------------------------------------------------
[ Jordan Husney: jordanh@remotepoint.com ]
[ Project LIMP Coordinator | Alps FAQ Maintainer ]
[ http://linux.remotepoint.com | http://alps.remotepoint.com ]
--
PHP Development Mailing List http://www.php.net/
To unsubscribe send an empty message to php-dev-unsubscribe@lists.php.net
For help: php-dev-help@lists.php.net