Remove @return PHPDocs where nothing is returned

This looks good to me. Tagging to be committed.

Committed to CVS HEAD. Thanks.

Re-opening this to accomplish before the release of 7.0. There are lots of added function with @return None that are silly.

I only see two incidents of @return None in Drupal 7 right now:
hook_cron() in modules/system/system.api.php
ajax_process_form() in includes/ajax.inc

These two should be fixed... But maybe my grep-fu is not as good as yours -- where else are you seeing them?

Actually, both of those function docs are terrible. The AJAX one, I'm not sure how to fix, and it may be on another issue...

Here's a patch for hook_cron() doc.

IMO, this is a bad standard. There is no way to distinguish missing docs from deliberate absence when using your IDE and so on.

What are you saying is a bad standard -- not having a @return if there is no return value? How long has that been our standard? Also, I think it's fairly standard across the software industry... such as:

http://java.sun.com/j2se/javadoc/writingdoccomments/#@return

I agree with jhodgdon in this case...
I never saw any standard saying you need to add "@return none" when there isn't any return value....

#11 is rtbc

To Moshe's defense, Java is different in that you have to explicitly declare the return type. So when you see 'void' in the method signature, you know there is no return value. There is no such equivalent in PHP of course.

#11: 516254hookcron.patch queued for re-testing.

#11: 516254hookcron.patch queued for re-testing.

I see moshe's point, but the idea of going around to every hook function, form submit/validate handler, testX() function, etc. and adding @return none fills me with absolute dread. Consistency is much easier to keep if we drop the @return on functions that don't return anything. And jhodgdon cites precedent, albeit from a strongly typed language.

Committed to HEAD.

If this isn't already documented in the coding standards, please do so.

It's in the standards already.