perlmod confuse doc perl array and hash (Origin: bugzilla #590161)

[doxygen]

status RESOLVED severity enhancement in component general for ---
Reported in version 1.5.9 on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

• DoxyDocs.pm (ID 139487)

On 2009-07-29 16:15:16 +0000, laszlo simon wrote:

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

On 2009-07-29 16:19:57 +0000, laszlo simon wrote:

Created attachment 139487
full perl output

problem at line 28

On 2009-07-29 16:24:24 +0000, laszlo simon wrote:

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

On 2009-07-29 16:24:53 +0000, laszlo simon wrote:

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

On 2009-07-29 16:27:14 +0000, laszlo simon wrote:

Sorry for the triple report anomaly.

On 2010-02-06 23:23:48 +0000, Dimitri van Heesch wrote:

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'
                }
              ]
            }
          ]
        },

On 2010-02-08 20:25:56 +0000, Dimitri van Heesch wrote:

Should be fixed in the next subversion update.

On 2010-02-21 12:57:45 +0000, Dimitri van Heesch wrote:

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.