Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrectly parsed Q_PROPERTY with 'long long' or 'long int' type (Origin: bugzilla #705190) #5250

Closed
doxygen opened this Issue Jul 2, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@doxygen
Copy link
Owner

doxygen commented Jul 2, 2018

status RESOLVED severity normal in component general for ---
Reported in version 1.8.4-GIT on platform Other
Assigned to: Dimitri van Heesch

On 2013-07-31 07:46:32 +0000, Matthäus Eismont wrote:

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:
SHA: 1e7e76a

On 2013-08-01 19:35:12 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next GIT update.

On 2013-08-05 12:10:06 +0000, Matthäus Eismont wrote:

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):

long int test_a

The stripped html output for 2):

long long test_b READ

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):

unsigned signed short test_c READ

The stripped html output for 4):

unsigned signed short int test_d

The same happens for other combinations like 'signed short' and 'unsigned short'.

On 2013-08-23 15:04:32 +0000, Dimitri van Heesch wrote:

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.

@doxygen doxygen closed this Jul 2, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.