mvriel/Docblox — comment on commit 589ebad154ba881b6998425d81eaf677023a5b3c
File: docs/PSR.md line 514
By ashnazg:

Yes, I meant that too (but forgot to say it ;-) ) -- keep "void" available, especially since a missing return means the doc generator should imply "void".

In my usage, I'm always going to specify "return void" explicitly, to tell my API readers "don't you be trying to use some return value here ". I would only ever put an explicit "return null" if I want my API readers to know to look for that null return. I tend to lean towards more explicity (e.g. "this page intentionally left blank") rather than letting "default behavior speak for itself", as the explicitness mitigates the potential of bad assumptions.

So, I think "return null" is valid and allowed, just like "return true" and "return false" would be. I also think "return void" is valid, and should be highlighted as the "default" when no return tag is used.

As an aside, I see "return void" used in phpDocumentor's own source code.