Bug 509893

Summary: Use of NULL macro instead of nullptr in C++ code
Product: [I don't know] kde Reporter: jshand2013
Component: generalAssignee: Unassigned bugs <unassigned-bugs-null>
Status: RESOLVED NOT A BUG    
Severity: normal CC: jshand2013, nate
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description jshand2013 2025-09-24 20:37:23 UTC 
Operating System: openSUSE Tumbleweed 20250923
KDE Plasma Version: 6.4.5
KDE Frameworks Version: 6.18.0
Qt Version: 6.9.2
Kernel Version: 6.16.8-1-default (64-bit)
Graphics Platform: Wayland
Processors: 12 × Intel® Core™ 7 150U
Memory: 16 GiB of RAM (15.3 GiB usable)
Graphics Processor: Intel® Graphics
Manufacturer: Dell Inc.
Product Name: Inspiron 16 5640

# Use of NULL macro instead of nullptr in C++ code

**Severity:** Low  
**Area:** Various  

## Description
Found ~10 occurrences of `NULL`. Prefer `nullptr` for type safety and clarity in modern C++.

## Evidence
Automated scan found ~10 occurrences across the codebase.

## Steps to Reproduce
1. Search for `\bNULL\b` in sources.

## Expected Behavior
All null pointer literals use `nullptr`.

## Actual Behavior
`NULL` persists in some places.

## Suggested Fix / Next Steps
- Mechanical replacement to `nullptr` where appropriate.
- Add clang-tidy check (`modernize-use-nullptr`).
Comment 1 Nate Graham 2025-09-24 20:58:03 UTC 
Please don't copy-paste the output of code "analysis" from ChatGPT or another AI. It isn't actionable.