Objective C method / property attribute decoration confuses parsing

[will-work]

Doxygen 1.9.2 (installed with executable), running on macOS Big Sur, MacBook Pro 2020 M1.

When a property or method declaration in an ObjC h file is decorated with the DEPRECATED_MSG_ATTRIBUTE attribute, Doxygen incorrectly parses the line:

• a property is interpreted as a method with name 'DEPRECATED_MSG_ATTRIBUTE'
• a method is misnamed 'DEPRECATED_MSG_ATTRIBUTE'

The expectation is that parsing ignores the attribute decoration entirely.

Example, containing one h file and Doxyfile:

Doxygen_bug.zip

Many thanks for your consideration.

[albert-github]

Looks like related to #5940

In the example the deprecated is now implemented by means of the usage of the @deprecated doxygen command, better would be that the DEPRECATED_MSG_ATTRIBUTE is implemented.

In the current situation I think that a workaround is to define DEPRECATED_MSG_ATTRIBUTE(x)= in the PREDEFINED setting.

[will-work]

Thank you for the pointer @albert-github - the workaround is absolutely acceptable, tested as working.

Many thanks for your quick help.

[albert-github]

Please don't close this issue, I think the real problem should still be addressed by doxygen i.e. make DEPRECATED_MSG_ATTRIBUTE automatically into a @deprecated entry.

[will-work]

Apologies, that was unintentional, I should have paid attention to the button text.

[albert-github]

I've just pushed a proposed patch, pull request #9060 that ignores the DEPRECATED_MSG_ATTRIBUTE and DEPRECATED_ATTRIBUTE.

The underlying, complex, problem of making DEPRECATED_MSG_ATTRIBUTE automatically into a @deprecated entry, still has to be addressed, see also #5940

[albert-github]

Code has been integrated in master on GitHub (please don't close the issue as this will be done at the moment of an official release).

[doxygen]

This issue was previously marked 'fixed but not released',
which means it should be fixed in doxygen version 1.9.4.
Please verify if this is indeed the case. Reopen the
issue if you think it is not fixed and please include any additional information
that you think can be relevant (preferably in the form of a self-contained example).

[will-work]

Thank you Dimitri, I will check.

…

On 5 May 2022, at 20:58, Dimitri van Heesch ***@***.***> wrote: This issue was previously marked 'fixed but not released', which means it should be fixed in doxygen version 1.9.4. Please verify if this is indeed the case. Reopen the issue if you think it is not fixed and please include any additional information that you think can be relevant (preferably in the form of a self-contained example). — Reply to this email directly, view it on GitHub <#9055 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEUR23DPXTTSA6LURCH75PTVIQR65ANCNFSM5MMXPVBQ>. You are receiving this because you modified the open/close state.