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

Replace Q_NULLPTR by nullptr #6614

Closed
wants to merge 1 commit into from
Closed

Replace Q_NULLPTR by nullptr #6614

wants to merge 1 commit into from

Conversation

gruenich
Copy link
Contributor

The former is a compatibility macro for code not allowed to use C++11.

The former is a compatibility macro for code not allowed to
use C++11.
@@ -5352,7 +5352,7 @@
<define name="Q_INTERFACES(X)" value=""/>
<define name="Q_LIKELY(expr)" value="expr"/>
<define name="Q_NAMESPACE" value=""/>
<define name="Q_NULLPTR" value="NULL"/>
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why was this changed?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It should have been removed completely, right?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would say leave it as it was, since we want to handle Q_NULLPTR in code that still uses it. The changes in the tests in qt.cpp should also be reverted. But then there are pretty much no functional changes left.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, I see, you want to test these old macros. Then it is better to leave everything as it is.

@gruenich gruenich closed this Jul 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants