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 640828 - Internal tags are not recognized for XML output in 1.7.2 and 1.7.3
Internal tags are not recognized for XML output in 1.7.2 and 1.7.3
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
unspecified
Other Windows
: Normal major
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2011-01-28 15:03 UTC by Ray Lefuel
Modified: 2012-11-18 11:11 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Ray Lefuel 2011-01-28 15:03:18 UTC
In the last 2 releases, the @internal tag is not recognized by the XML output.

In versions 1.7.1 and earlier, the \internal tag would generate an <internal/> tag in the <detaileddescription> structure of the XML output; it no longer does this.  Internal docs are now indistinguishable from public docs.

Source sample:

typedef enum {
    /// @internal
    SAMPLE_API_ENUM = 50
} sample_enum;

1.7.1 Output:

        <enumvalue id="sampleapime_8h_1a7f9d02e9a1fafd2b6ab3ce471344b381ae3699e9ee5a0d4ed0d33438891f8f17e" prot="public">
          <name>SAMPLE_API_ENUM</name>
          <initializer> 50</initializer>
          <briefdescription>
          </briefdescription>
          <detaileddescription>
<internal/>
          </detaileddescription>
        </enumvalue>

1.7.2 and 1.7.3 Output:

        <enumvalue id="sampleapime_8h_1a7f9d02e9a1fafd2b6ab3ce471344b381ae3699e9ee5a0d4ed0d33438891f8f17e" prot="public">
          <name>SAMPLE_API_ENUM</name>
          <initializer> 50</initializer>
          <briefdescription>
          </briefdescription>
          <detaileddescription>
          </detaileddescription>
        </enumvalue>
Comment 1 Dimitri van Heesch 2011-01-29 16:08:49 UTC
Confirmed. Should be fixed in the next subversion update.
Comment 2 Dimitri van Heesch 2011-03-28 14:19:18 UTC
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.7.4. 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.