Fixed integer overflow in stream-logger-killcursor-001.phpt
Merge Pull Request #442

* pull-request/442:
  Fixed integer overflow in stream-logger-killcursor-001.phpt
Merge branch 'v1.4'

* v1.4:
  Fixed integer overflow in stream-logger-killcursor-001.phpt
Fixed PHP-657: Deprecate MongoCursor::slaveOkay
Remove the leftover 'fd' property that was killed recently (in 1.4)

See PHP-794
Fix tests
Merged Pull Request #428

* pull-request/428:
  Fix tests
  Remove the leftover 'fd' property that was killed recently (in 1.4)
  Fixed PHP-657: Deprecate MongoCursor::slaveOkay
Fixed tests after added deprecation notice.
Merged pull request #445
Merge branch 'v1.4'
Fixed PHP-818: Add deprecation notices to usage of Mongo.

For the tests, I also swapped to using "MongoClient" by default and looked at
individual tests at what they were testing to decide whether to go with
"old_mongo" specifically or mongo/new_mongo() or equivalents. I guess some
choices could be debated though.

In one case (tests/generic/bug00635.phpt) I changed the expected output (beyond
deprecation notices), but this test was testing something unrelated to w=0/w=1.
Merged pull request #443
Fixed PHP-774: Mark MongoCollection::toIndexString as deprecated.

For this to work, I also had to separate it out as otherwise our own
ensureIndex() would throw a deprecation warning.
Fixed NULL-dereference error and ZTS build.
Fixed tests for PHP 5.2.
Fixed another NULL-dereference

And adding missing tests for deleteIndex/deleteIndexes so that we can see that
this failed. However, I noticed a really annoying behaviour for deleteIndex(
string ). Instead of it dropping an index with the name "string", it uses it as
a field name to append "_1" too. So you can not use it at all for user-named
indexes. I've added issue PHP-817 to the 2.x milestone to sort that out.
Merged pull request #434
Fixed PHP-804: Deprecate Mongo::connectUtil.
Merged pull request #436
Throw deprecation notices for properties mark as ZEND_ACC_DEPRECATED

PHP doesn't support deprecating properties so we have to overload the
default property handler and lookup the property flags to issue the
warning