Standardize on either '@param bool $foo' or '@param boolean $foo' and document the decision.

When in doubt, we do as PEAR does, which according to http://pear.php.net/manual/en/standards.sample.php is 'bool'.

And please reserve the "Needs committer feedback" tag to things that are deadlocked or otherwise actually need a committer to take time away from committing patches to comment on. :)

Wow... I did not realize that a boolean value was so inconsistent in existing core documentation. I vote that we apply the change-boot-to-boolean.patch. bool should be fully spelled out and not abbreviated.

Before that patch is applied though, I would respectfully request that we also correct each of the incorrect docblocks that the resulting patch touches. For instance, in 'abstract class FileTransfer', there are a number of @param docs without explanation right after another. Also, in 'class UserRolesAssignmentTestCase extends DrupalWebTestCase', the @param explanation is not indented on the next line. While it will not clean up all of the offending docblocks, such fixes will make the documentation at least a bit better/compliant.

Whoops... cross-post.

Before this is closed, shouldn't we roll a patch for the examples section of the document standards? I am thinking we should also include an inline comment stating not to use 'boolean'. The other thought is wondering if @param bool or @param boolean currently exists in the D7 code base.

I was thinking of a patch for http://drupal.org/node/1354 something along the lines of:

* @param array $myarray
* An array.
* @param bool $flag // Nota bene: use bool and not boolean <-- added via patch
* A boolean variable (with values like TRUE or FALSE). <-- added via patch
* @param int $myinteger
* An integer.
* @param string $mystring

Hopefully this makes sense and @webchick can apply the resulting patch to document for all about her decision in this issue.

Re #9 - Sorry @pillarsdotnet.... Other than the two lines regarding bool/boolean, the rest of that text came directly out of Documenting functions and methods.

When we go in to correct/define the bool/boolean issue, we also need to go through and add type hinting throughout many of the examples on that page. We also should probably correct the example documentation as you proposed in #10.

Curiously, both bool and boolean work when casting a variable to boolean. :-) Doesn't affect the decision, I just thought it was amusing. (If one of them had actually broken, that would have been our answer.)