"inheritdoc" Not Recognized in XML Style Documentation (Origin: bugzilla #666527)

[doxygen]

status RESOLVED severity normal in component documentation for ---
Reported in version 1.7.6.1 on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

• Example.cs (ID 203880)
• fix_for_inheritdoc_xml.diff (ID 208582)

On 2011-12-19 14:40:51 +0000, John Werner wrote:

Created attachment 203880
Example code showing problem with ""

When using XML style special commands (i.e. when developing in MS Visual Studio), the "inheritdoc" command is not recognized. If it is used as regular Doxygen special command (e.g. "@inheritdoc"), it is recognized.

More specifically, the following forms will result in Doxygen reporting "warning: Unsupported xml/html tag found"

///
///

The following will work as expected

/// @inheritdoc

Example code illustrating the problem is attached.

On 2011-12-26 14:06:47 +0000, Dimitri van Heesch wrote:

The tag is not a valid C# XML comment as far as I know. Can you point at a specification where it is explained?

On 2011-12-29 17:56:14 +0000, John Werner wrote:

It's used by NDoc and GhostDoc. Here are a couple of references.

• http://stackoverflow.com/questions/311363/net-xml-docs-inheriting-documentation
• http://stackoverflow.com/questions/824007/ways-to-synchronize-interface-and-implementation-comments-in-c-sharp
• http://www.ewoodruff.us/shfbdocs/html/79897974-ffc9-4b84-91a5-e50c66a0221d.htm

On 2012-02-03 13:30:03 +0000, John Werner wrote:

Not as much a comment as a question:

Why did this go to Unconfirmed? The use of "" in C# comments is documented in other places. NUnit doesn't support it, but does support "/// @inheritdoc".

On 2012-02-28 13:42:15 +0000, John Werner wrote:

Created attachment 208582
Patch to add support to Doxygen

This patch was created for 1.7.6 and then successfully applied to our local build 1.7.5. It adds support to for using "inheritdoc" as an XML tag ().

On 2012-03-03 15:42:43 +0000, Dimitri van Heesch wrote:

Thanks, I'll include the patch in the next subversion update.

On 2012-05-19 12:26:43 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.1. 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.