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

C and C++, simple type specifiers should be allowed in any order #9917

Closed
jakobandersen opened this issue Nov 30, 2021 · 1 comment
Closed

Comments

@jakobandersen
Copy link
Contributor

Describe the bug

In C and C++ all of the following types are valid and the same:

  • unsigned long int
  • unsigned int long
  • long unsigned int
  • long int unsigned
  • int unsigned long
  • int long unsigned
    The same goes for all other simple type specifier sequences.

Since #9547 only those on the form were accepted.

How to Reproduce

Have a declaration with a type not on the form above.

Expected behavior

No response

Your project

N/A

Screenshots

No response

OS

Any

Python version

Any

Sphinx version

= 4.2.0

Sphinx extensions

No response

Extra tools

No response

Additional context

Discovered via breathe-doc/breathe#771

@jakobandersen
Copy link
Contributor Author

Fixed via #9918.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 5, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant