Switch to nullptr
Bug #1407335 reported by
Chris Coulson
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Oxide |
Fix Released
|
Low
|
Chris Coulson | ||
Bug Description
We're currently using NULL everywhere (which is just 0), and Chromium switched to nullptr some time ago. We should try to do the same, although I'm not sure whether things like QScopedPointer and QPointer support it
Related branches
| Changed in oxide: | |
| importance: | Undecided → Low |
| status: | New → Triaged |
| Changed in oxide: | |
| assignee: | nobody → Chris Coulson (chrisccoulson) |
| milestone: | none → branch-1.5 |
| status: | Triaged → Fix Released |
To post a comment you must log in.
