Created attachment 167187 [details]
documentation screenshot part 1

Created attachment 167188 [details]
documentation screenshot part 2

In Java or C++ I have following function declaration:

public String getText() {
}

How can I add the return datatype of a function to the documentation with php??

I got the following warning and the member variable is not documented:

php/core/db/Cache.class.php:22: warning: documented function `core::db::Cache::string' was not declared or defined.

my code looks like:

/**
 * Class for caching values.
 */
class Cache
{

  /**
   * Name of the cache
   * @var string
   */
    private static $cache = null;
}

If I remove the @var line doxygen will work without warning and show the documentation but without the type, of course.
But I need the @var line for the code assist functions in netbeans and eclipse.

Yes, it seems does not work @var and the description of  variable (public, protected or private).
It works only with phpDoc... :(

I got this working with this syntax

class Mine {
   /**
    * Definition of variable
    * @var string $var
    */
   private $var = array();
}

Though it would make sense to NOT have to respecify the variable name everytime.

This is tested on doxygen 1.7.3

And here is the explanation of WHY it's doing this..

(documentation for @fn which @var is treated as)
http://www.stack.nl/~dimitri/doxygen/commands.html#cmdfn

So the issue here is differences between how PHPDoc interprets @var (which all the IDEs seem too go by) and how Doxygen interprets @var..  And of course the frustrating thing is, I like the doxygen output MUCH better than PHPDoc.  So having some kind of PHP "exception" for @var in doxygen would be really appreciated.

*** Bug 656778 has been marked as a duplicate of this bug. ***

I've posted a workaround on StackOverflow: http://stackoverflow.com/a/8472180/276152

It is just a simple regexp that can be used as input filter to make the member declaration more C-like, and this so, allow Doxygen lexer to get the type info. 

It also removes @var annotation as it has a different meaning with Doxygen than in phpDoc.

Be free to use and extend as public domain and/or the Doxygen license.

Quick fix: INPUT_FILTER = "sed -e 's/@var\s/@see /'"

It is not perfect, but it can help when more complicated regexps don't fit your code. It is better than omitting the @var altogether since the information about type is not lost, only moved to the description.

Regarding the @var the docuenation states (chapter about special commands):

24.51 \var (variable declaration)
Indicates that a comment block contains documentation for a variable or enum value (either global or as a member of a class).

and on the top of the chapter:
• If (round) braces are used the argument extends until the end of the line on which the command was found.

Not documented is the behavior of php regarding the datatype.

A small example here is:
<?php
/** \file */

/** @var $v1
  *  variable without data type
  */
$v1 = 7;

/** @var int $v2
  *  variable with data type
  */
$v2 = 7;

/** @var int
  *  just data type
  */
$v3 = 7;

?>


So in my opinion the problem is usage, and the issue can be closed as such.

Regarding the documentation omission:
I've just pushed a proposed patch to github (pull request 718, https://github.com/doxygen/doxygen/pull/718).

Hello, I was seeing this problem and I couldn't solve in anyway.
But seeing that a patch was proposed on git, I'm waiting for it to be approved.

Since the patch indicates that the @var documentation should be as follows (as I understood it):

/**
*
* @var type
* documentation
**/
scope $var

For those using Eclipse, I believe it doesn't allow you to do this, because it requires that every documentation for unformatted commands (I believe the @var and such commands can't be modified by formatters) has to be on a single line.

So I've created this code/regex for a input filter so that it automatically breaks a line after the TYPE specification:


// inserting a linebreak after '@var type'
$regexp = '/(.+@var .+?)(\s)(.+)/';
$mod = explode( PHP_EOL, $source );
$match = preg_grep( $regexp, $mod );
foreach ( $match as $key => $line )
{
  $mod[ $key ] = preg_replace( '/(?<!@var)\b(\s)\b/', PHP_EOL . "    *           ", $line, 1 );
}
$source = implode( PHP_EOL, $mod );

this code turns

/**
* @var int blablabla
**/

into 

/**
* @var int
*           blablabla
**/

If you want to use the $varName also, you just have to modify the regex code a little bit. If you don't use '@' but use '\' instead, just modify the regex too. 

Let's hope this pull gets merged soon ;).

The pull request is just small explanation in the documentation. No code changes.
Be aware of the possible side effects of the spaces before blablabla and markdown support.

As discussed in https://github.com/doxygen/doxygen/pull/734 , Doxygen has moved its issue tracking to 

   https://github.com/doxygen/doxygen/issues

All Doxygen tickets in GNOME Bugzilla have been migrated to Github. You can subscribe and participate in the new ticket in Github. You can find the corresponding Github ticket by searching for its Bugzilla ID (number) in Github.

Hence I am closing this GNOME Bugzilla ticket.
Please use the corresponding ticket in Github instead. Thanks a lot!