GNOME Bugzilla – Bug 705190
Incorrectly parsed Q_PROPERTY with 'long long' or 'long int' type
Last modified: 2013-08-23 15:04:32 UTC
It seems like doxygen is not able to parse these types correctly. This issue is most likely related to this issue and describes the same problem: https://bugzilla.gnome.org/show_bug.cgi?id=700385 The related commit is: https://github.com/doxygen/doxygen/commit/1e7e76afce339b779c7c44bf3640b277586c1a5e
Confirmed. Should be fixed in the next GIT update.
The problem with 'long int' seems to be fixed. However, there seems to be a recursion problem with 'long long'. For example: 1) Q_PROPERTY(long int test_a READ get_test_a) // Ok. 2) Q_PROPERTY(long long test_b READ get_test_b) // Wrong. The stripped html output for 1): <tr> <td class="memItemLeft"> long int </td> <td class="memItemRight"> test_a </td> </tr> The stripped html output for 2): <tr> <td class="memItemLeft"> long long test_b </td> <td class="memItemRight"> READ </td> </tr> Or even absurd: Q_PROPERTY(unsigned signed short test_c READ get_test_c) // Wrong. Q_PROPERTY(unsigned signed short int test_d READ get_test_d) // Ok. The stripped html output for 3): <tr> <td class="memItemLeft"> unsigned signed short test_c </td> <td class="memItemRight"> READ </td> </tr> The stripped html output for 4): <tr> <td class="memItemLeft"> unsigned signed short int </td> <td class="memItemRight"> test_d </td> </tr> The same happens for other combinations like 'signed short' and 'unsigned short'.
This bug was previously marked ASSIGNED, which means it should be fixed in doxygen version 1.8.5. 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.