Fix return value of _writeBlock

[Hipska]

Fixes #52

[mcdruid]

Thanks.

The failure on PHP 5.4 is unrelated; we're likely to remove that check soon (discussion in #51). Looks like we also need to tidy up the test config.. again unrelated.

I don't think we necessarily need to add specific tests to show the new return value if _writeBlock fails (although if we can think of an easy way to do that.. great).

However, we should reassure ourselves that method is exercised by the test suite - and therefore that this change doesn't introduce a regression during normal / successful operation.

[Hipska]

Thanks @mcdruid. Do you expect anything from me?

[Hipska]

@mcdruid any feedback? I would like to get this one landed soon.

[mcdruid]

Sorry I meant to reply sooner.

Generally I would avoid starting to refactor anything that's not absolutely necessary to change in order to address a specific issue.

I'm trying to make some progress on tweaking the test config as part of retiring support for ancient PHP versions, hoping that will unblock getting a couple of changes into a new release.

However, I am not a fully-fledged PEAR maintainer (in terms of knowledge of some of the more arcane processes apart from anything else) and am not able to do full releases of this project myself.

So I'm afraid I don't know how soon this - and other fixes - will get unblocked and make it into a release.

[Hipska]

I'm just wondering what needs to be done on my part to get this PR accepted and merged..

[ashnazg]

@mcdruid , I'll see if I can make some time this weekend to help catch things up here.

[mcdruid]

Thanks @ashnazg

Rather than going into the details of what I think we need to do here, I spun up #57