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 590161 - perlmod confuse doc perl array and hash
perlmod confuse doc perl array and hash
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.5.9
Other Windows
: Normal enhancement
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
: 590159 590160 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-07-29 16:15 UTC by laszlo simon
Modified: 2010-02-21 12:57 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
full perl output (935 bytes, text/plain)
2009-07-29 16:19 UTC, laszlo simon 		Details

Description laszlo simon 2009-07-29 16:15:16 UTC 
When perl output generated on the following example.c:

  /*@{*/
  #define EXAMPLE (example)
  /*@}*/
  /** \see EXAMPLE */
  extern int example;

There is a confusing item in the output perl package:

  doc => [
    see => [
      {
        type => 'url',
        link => 'example_8c_113b633378ea20dff6ff220caedb3e01d',
        content => 'EXAMPLE'
      }
    ]

'doc=>[...]' declared to array, but initialised with a hash 'see => ...'.
Perl can process it, hash will separated to key and value and will form an array [key, value] like this:

  doc->[0] = 'see';
  doc->[1] = { ... };

but it is formally incorrect, and hardly processable. 

Tested with 1.5.9 windows build
Comment 1 laszlo simon 2009-07-29 16:19:57 UTC 
Created attachment 139487 [details]
full perl output

problem at line 28
Comment 2 laszlo simon 2009-07-29 16:24:24 UTC 
*** Bug 590159 has been marked as a duplicate of this bug. ***
Comment 3 laszlo simon 2009-07-29 16:24:53 UTC 
*** Bug 590160 has been marked as a duplicate of this bug. ***
Comment 4 laszlo simon 2009-07-29 16:27:14 UTC 
Sorry for the triple report anomaly.
Comment 5 Dimitri van Heesch 2010-02-06 23:23:48 UTC 
Hi Laszlo,

I assume it is ok if the output is corrected as follows:

            detailed => {
              doc => [
                {
                  type => 'text',
                  content => 'Some text '
                },
                {
                  see => [
                    {
                      type => 'text',
                      content => 'EXAMPLE'
                    }
                  ]
                }
              ]
            },
Comment 6 Dimitri van Heesch 2010-02-08 20:25:56 UTC 
Should be fixed in the next subversion update.
Comment 7 Dimitri van Heesch 2010-02-21 12:57:45 UTC 
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.6.3. Please verify if this is indeed the case. Reopen the
bug if you think it is not fixed and please include any additional information 
that you think can be relevant.