----- Original Message ----- From: "Tom Rogers" <[EMAIL PROTECTED]> > Most programs will crash with null pointers so I operate with error > reporting set to E_ALL and it helps when these sort of things happen. > A function should never trust what it is being fed :) so your solution > is the right way, I don't think you will get much sympathy from the > developers but it would not hurt to tell them.
One of the first things I did was change the error reporting to E_ALL (and now have it on E_ALL permanently), but I initialise all my variable names (not the same thing as accessing unassigned array elements) so this didn't produce anything. ----- Original Message ----- From: "Curt Zirzow" <[EMAIL PROTECTED]> > Before screaming bug at the developers I would strongly suggest: > > . making a very simple example of code that can reproduce (or in > this case irraticly reproduce) the crash. The problem with all this, as Mike has suggested, is that the errors you get change as you change totally unrelated parts of the code - reducing it down seems likely to "fix" them even if I leave in the bits that I suspect cause it! Hopefully I'll have a bit of time to see what I can do, though. cheers, Martin -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
