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

Cleanup: Replace NULL with nullptr #13168

Closed
wants to merge 1 commit into from
Closed

Cleanup: Replace NULL with nullptr #13168

wants to merge 1 commit into from

Conversation

Vertexwahn
Copy link
Contributor

At several places, NULL and nullptr were mixed. This commit cleans this up and switches NULL to nullptr where appropriate.

At several places, NULL and nullptr were mixed. This commit cleans this up and switches NULL to nullptr where appropriate.
@brandjon brandjon requested a review from philwo March 7, 2021 18:41
@brandjon
Copy link
Member

brandjon commented Mar 7, 2021

Philipp, do you know who we can triage this to? Looks fairly simple but I'm not a C++ person or familiar with our C++ code.

@brandjon brandjon removed the request for review from tetromino March 7, 2021 18:42
@philwo philwo self-assigned this Mar 10, 2021
@philwo philwo added P1 I'll work on this now. (Assignee required) team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website type: feature request labels Mar 10, 2021
@philwo
Copy link
Member

philwo commented Mar 10, 2021

@brandjon I'll try to import this, maybe it'll just go through without issues. :)

@philwo
Copy link
Member

philwo commented Mar 10, 2021

@Vertexwahn Thank you for this. The presubmit tests are running at the moment and when they pass, it'll be merged automatically. :)

Just FYI, while importing I noticed a few more lines in process.cc that still used NULL (e.g. https://cs.opensource.google/bazel/bazel/+/c789d78fa2a3fb760e99963bac5000f49747cc88:src/main/native/windows/process.cc;l=175-178) and I fixed them to use nullptr instead, too. Hope that was fine from your point of view.

@bazel-io bazel-io closed this in 26c7e10 Mar 10, 2021
larsrc-google pushed a commit to larsrc-google/bazel that referenced this pull request Jul 28, 2021
At several places, NULL and nullptr were mixed. This commit cleans this up and switches NULL to nullptr where appropriate.

Closes bazelbuild#13168.

PiperOrigin-RevId: 362043567
larsrc-google pushed a commit to larsrc-google/bazel that referenced this pull request Jul 30, 2021
At several places, NULL and nullptr were mixed. This commit cleans this up and switches NULL to nullptr where appropriate.

Closes bazelbuild#13168.

PiperOrigin-RevId: 362043567
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla: yes P1 I'll work on this now. (Assignee required) team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website type: feature request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants