I don’t know how I arrived here, nor I am using any of this techniques (I use multicurl for massive querying), but just a little bit of advise regarding the json_encode.

There is a bug with large integers and the PHP json_encode/decode functions in 32-bit machines (mere mortals usually use that). If you do not have a 64-bit machine the integers decoded will be corrupted, and you will have wrong twitter IDs.

You should either use a 64-bit machine or surround the numerical values with “” before decoding the response (treat them as strings).

My 5 cents

Nice article. BTW, instead of this:

if(isset($array['id']) AND $array['id'] > 0)

the following is more concise:

if (! empty($array['id']))

!empty works just like isset in that it will check that the variable/array index is set but also has the added value of ensuring that the value is not an “empty” value like false, 0, or NULL.

One precaution though…if you are accepting 0 as a valid value, you don’t want to use empty because a value of 0 will cause empty to return false.

BTW, given the fact that you have set “error_reporting(E_ALL)” you most certainly will be getting a NOTICE if you omit the empty or isset call. If you didn’t see the notice, it could be that you have display_errors = false.

-Wil Moore III

Your object is unusable a second time anyway, since you’re not resetting $this->done.

Once again, great series.

The isset() appears to be unnecessary. However, I might still keep it for two reasons: first, it explicitly checks to make sure that the ID value is set, and even though that condition would be satisfied by the second check, it’s obvious as soon as you look at it. Second, because undefined variables will emit errors (for example, if you test for the presence of $value but don’t define $value you get a notice), it’s a good practice to use isset() to test for value initialization before testing for the actual value.

Is there any reason why you chose to do an isset along with checking if the id was greater than 0? (line 173)