> (a) Failure return value of FETCH_RESOURCE and the default return value -
> should we change it to be FALSE?  Today it's NULL, which is inconsistent
> with most of the functions in PHP which return FALSE on failure.  The
> downside is that changing it may break scripts that check the return value
> with === or !==

+1. I think this is a good idea. We've already had bugs where people were 
using === and !== to determine wether the function had worked or not. Since 
the resource retrieval (or argument parsing) failed they received unexpected 
NULL (rather then the documented FALSE) and ended up running an unterminated 
loop.

> (b) Default inclusion of the SOAP extension

+0. Overall it seems like a good idea. However, I am not sure how stable is 
SOAP extension after massive revisions Dmitry did and the TODO list still has 
quite a few entries in it. Do we really want to halt (feature freeze) 
development at this point?

Ilia

-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to