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
Global: change from NULL to nullptr #12648
Global: change from NULL to nullptr #12648
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can't manually change the generated output for Lua.
@WickedShell san. Comments Thanks. |
@muramura I'm not actually fully sure it's the correct change for the Lua code either way though, as the structure is getting passed to C code, and the sentinel is supposed to just be |
I think it is better to use nullptr defined in C ++ source to solve the NULL problem. |
0856366
to
b3e4524
Compare
Reworked and remove change on Lua files
I've removed the dev-call-topic. I suspect this hasn't been tested. I'm afraid that all changes need to be tested so we can be sure they don't break anything. Even NFC. If that's not possible, let's close this. |
a flight test should be enough to validate this. |
A flight test isn't enough to validate this. We don't cross all of the relevant codepaths in a single flight. This is now conflicting horribly, and it will probably be easier to redo from scratch. However, I suggest a better way forward would be to just stay vigilant about eliminating I'm going to close this one as a lost cause. I'm not convinced a similar PR will gain much traction - it doesn't buy us that much. That being said, I'll look at any against |
For NULL pointers, nullptr is more appropriate for C++.