After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 153380 - warning and link problems
warning and link problems
Status: RESOLVED INCOMPLETE
Product: doxygen
Classification: Other
Component: general
1.2.x
Other Linux
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2004-09-22 05:34 UTC by Matthias Klose
Modified: 2014-12-10 05:02 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Matthias Klose 2004-09-22 05:34:26 UTC
[forwarded from http://bugs.debian.org/136028
 forwarded by email as well, but no trace in the BTS]

I think I've found a couple of bugs. The first is with function parameter 
detection. The new doxygen version generates many warning regarding missing
variable in function definitions. For example for this function
/**
 * @fn aggiorna_par_rx_can(unsigned int,unsigned char*,unsigned char)
 * @param id_msg msg identifier
 * @param vect_rx answ. vect
 * @param length_mess message lenght
*/
void aggiorna_par_rx_can(unsigned int id_msg,
    unsigned char* vect_rx,
    unsigned char length_mess)
{
...
}

I get the following errors:

can.c:449: Warning: argument `id_msg' of
command @param is not found in the argument list of
aggiorna_par_rx_can(unsigned int, unsigned char *vect_rx, unsigned char)
can.c:449: Warning: argument
`length_mess' of command @param is not found in the argument list of
aggiorna_par_rx_can(unsigned int, unsigned char *vect_rx, unsigned char)
adb800/can.c:449: Warning: The following
parameters of aggiorna_par_rx_can(unsigned int, unsigned char *vect_rx,
unsigned char) are not documented:
  parameter int
  parameter char

But it generates the right output. I'm sure the problem is in the latest
doxygen version. 

The second problem is with the automatic link generation. I noticed that
when I define a group that assemble together functions from different
files, many anchor links in each files, refer to the local file instead
of the group file. For example if I have two file with functions:
a.c
	foo()
	bar()
b.c
	barfoo()
	foobar()

and I define a group "c" that assembles foo() and foobar(), I'll have
the anchor links in a.c point to a_c.html#a1 instead of group_c.html#a1.
This is true for in-functions anchor links (that is, the anchor defined
in the function code) but not for the header links (that is, links defined 
at the beginning of a_c.html that groups functions, variables, definitions, 
etc).

thank you for your help,
grazie dell'aiuto,
		pietro

Luca Filipozzi wrote:

Hi Dimitri,

the following bugs have been reported against Doxygen.  Can you let me
know if you consider them to be valid and whether you plan to fix them?

Thanks very much,

Luca

--------------------------------------------------------------------------------
#136028: doxygen: warning and link problems - Part A: (I think this is fixed.)
  I think I've found a couple of bugs. The first is with function parameter 
  detection. The new doxygen version generates many warning regarding missing
  variable in function definitions. For example for this function
  /**
   * @fn aggiorna_par_rx_can(unsigned int,unsigned char*,unsigned char)
   * @param id_msg msg identifier
   * @param vect_rx answ. vect
   * @param length_mess message lenght
  */
  void aggiorna_par_rx_can(unsigned int id_msg,
      unsigned char* vect_rx,
      unsigned char length_mess)
  {
  ...
  }

  I get the following errors:

  can.c:449: Warning: argument `id_msg' of
  command @param is not found in the argument list of
  aggiorna_par_rx_can(unsigned int, unsigned char *vect_rx, unsigned char)
  can.c:449: Warning: argument
  `length_mess' of command @param is not found in the argument list of
  aggiorna_par_rx_can(unsigned int, unsigned char *vect_rx, unsigned char)
  adb800/can.c:449: Warning: The following
  parameters of aggiorna_par_rx_can(unsigned int, unsigned char *vect_rx,
  unsigned char) are not documented:
    parameter int
    parameter char

  But it generates the right output. I'm sure the problem is in the latest
  doxygen version. 
  I think I've found a couple of bugs. The first is with function parameter 
  detection. The new doxygen version generates many warning regarding missing
  variable in function definitions. For example for this function
  /**
   * @fn aggiorna_par_rx_can(unsigned int,unsigned char*,unsigned char)
   * @param id_msg msg identifier
   * @param vect_rx answ. vect
   * @param length_mess message lenght
  */
  void aggiorna_par_rx_can(unsigned int id_msg,
      unsigned char* vect_rx,
      unsigned char length_mess)
  {
  ...
  }

  I get the following errors:

  can.c:449: Warning: argument `id_msg' of
  command @param is not found in the argument list of
  aggiorna_par_rx_can(unsigned int, unsigned char *vect_rx, unsigned char)
  can.c:449: Warning: argument
  `length_mess' of command @param is not found in the argument list of
  aggiorna_par_rx_can(unsigned int, unsigned char *vect_rx, unsigned char)
  adb800/can.c:449: Warning: The following
  parameters of aggiorna_par_rx_can(unsigned int, unsigned char *vect_rx,
  unsigned char) are not documented:
    parameter int
    parameter char

  But it generates the right output. I'm sure the problem is in the latest
  doxygen version. 

--------------------------------------------------------------------------------
#136028: doxygen: warning and link problems - Part B:
  The second problem is with the automatic link generation. I noticed that
  when I define a group that assemble together functions from different
  files, many anchor links in each files, refer to the local file instead
  of the group file. For example if I have two file with functions:
  a.c
    foo()
    bar()
  b.c
    barfoo()
    foobar()

  and I define a group "c" that assembles foo() and foobar(), I'll have
  the anchor links in a.c point to a_c.html#a1 instead of group_c.html#a1.
  This is true for in-functions anchor links (that is, the anchor defined
  in the function code) but not for the header links (that is, links defined 
  at the beginning of a_c.html that groups functions, variables, definitions, 
  etc).
Comment 1 bastien roucaries 2013-05-27 18:28:54 UTC
Any news of this bug ?
Comment 2 Dimitri van Heesch 2013-10-13 17:22:56 UTC
Can you please attach a self-contained example (source+config file in a tar or zip) that allows me to reproduce the problem?
Comment 3 André Klapper 2014-12-10 05:02:43 UTC
(In reply to comment #2)
> Can you please attach a self-contained example (source+config file in a tar or
> zip) that allows me to reproduce the problem?

Hi Matthias, 
I am closing this bug report as no updated information has been provided.
Please feel free to reopen this bug if you can provide the information that was asked for in a previous comment.