> 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 ---------------------------------------------------------------------------- -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
