Description: ------------ When using the PEAR CS, phpcs complains "Missing @return tag in function comment" for functions which do no have a return statement. Although it is possible to do something like @return void, a better solution would be for phpcs to not require the comment for functions/methods where nothing is being returned.

You should be writing "@return void" to make it clear that your lack of return value is not a mistake. In the Squiz standard, PHPCS will actually confirm that any function claiming to return void is not returning a value anywhere, which is what I personally prefer. As this is simple a matter of opinion, I'm going to mark this report as bogus. If you'd like a specific exception added to the PEAR standard, please email the PEAR QA or dev list. If there is an exception already made in the standard that I haven't seen, just point it out for me and I'll reopen the bug.

Hi Greg, That's fine. I actually couldn't find anything in the actual CS about whether or not a return type should be specified. I could only find one discussion which suggested that at least as far as phpDocumentor is concerned, it's better to leave it out: http://stackoverflow.com/questions/2061550/phpdoc-return-void-necessary I think your point about explicitly marking the method as not having a return value is a good idea though. I'll do that. Thanks!