Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:15261
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <64467.207.192.181.138.1110070268.squirrel@secure.fieldpost.com>
In-Reply-To: <4e89b42605030515232be43775@mail.gmail.com>
References: <422A09BB.7080409@dtlink.com> <422A1047.7080303@teh.ath.cx>
	<64721.207.192.181.138.1110056745.squirrel@secure.fieldpost.com>
	<4e89b42605030515232be43775@mail.gmail.com>
Date: Sat, 5 Mar 2005 19:51:08 -0500 (EST)
To: "Wez Furlong" <kingwez@gmail.com>
Cc: "Matthew Charles Kavanagh" <matthew@teh.ath.cx>,internals@lists.php.net
Reply-To: yml@dtlink.com
User-Agent: SquirrelMail/1.4.2
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Importance: Normal
Subject: Re: [PHP-DEV] PHP 5.0.3 losing $this
From: yml@dtlink.com ("Yermo Lamers")


> The problem you're having is not giving the right information.  For
> instance, the buffer overrun errors would be an ideal thing to attach
> to your bug report.

The buffer overruns are the separate bug in PHP 4 as in
http://bugs.php.net/31508.

The PHP 5 is not encountering a buffer overrun; it just loses $this.

> Write good bug reports.  There is something of an art to it,
> especially for the harder to pin-down problems.  I just glanced
> through your script, and the mere fact that you have to search for the
> bug shows that the test script is too large.

So what do you do when you can't reduce it down any further? I spent two
days putting that script together in a trial and error fashion until I
finally got something that seemed reasonably small in size.

It's 8 lines, not including the supporting classes; and those classes are
very simple.

There error it generates is completely obvious. "$this is not an object".
Hmm. how could that be?

It is entirely unreasonable to think that all bugs are going to be reduced
down to a few lines of code. Maybe if you're doing trivial things .. but
when dealing writing complicated systems it's often not so straight
forward.

> The bottom line is that PHP is a free open source project, powered by
> volunteers; show some respect for our free time by taking the time to
> refine the report to the smallest possible test case.

I spent 16 hours producing that test case. It took countless runs. The
body of code that it comes from includes over 61,000 lines of code. You
see my problem.

If someone doesn't have enough time to at least look at it they could at
least point me in a direction so I can start delving into it. I understand
it's an open source project and I am trying to contribute where I can.

I'm not saying fix this for me. I'm saying "Where do I go next if I can't
produce the small script". The answer seems to be "you're out of luck".

Maybe the answer is "You need to pay someone to fix it", or "check out
this section of the parser yourself" or "try this patch" or "give us a
login and get on the phone with us and help us do this".

Some next step because I have to get this fixed.

The answer I keep getting is "oh well, we're too busy, you have no options
if you can't reproduce it in 20 lines".

-- Yermo

----------------------------------------------------------------------------
DTLink Software                                 http://www.dtlink.com
       Desktop Software and Web Applications
----------------------------------------------------------------------------