Err .. I don't agree. Null means no data False means error.
Maybe historically (PHP-wise) it does.
But the way I see it, every fetch() can 'fail' for two reasons: an expected well-defined reason (eof), and an unexpected undefined reason (error). Labelling the well-defined reason as 'false' and the undefined reason as 'null' is really quite defendable.
This isn't something I'd like to see changed. I actually think there are probably lots of people who do !== false and we could screw up a lot of scripts. I see the advantage of being able to tell the difference but I think it's not big enough to change it now.
Andi
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
